Skip to content

ASoC: SOF: soundwire: add init soundwire support#823

Merged
plbossart merged 1 commit intothesofproject:topic/sof-devfrom
xiulipan:pr/abi35
Apr 17, 2019
Merged

ASoC: SOF: soundwire: add init soundwire support#823
plbossart merged 1 commit intothesofproject:topic/sof-devfrom
xiulipan:pr/abi35

Conversation

@xiulipan
Copy link
Copy Markdown

Add soundwire dai type and update ABI version.

Signed-off-by: Pan Xiuli xiuli.pan@linux.intel.com

Fix #822

@ranj063
Copy link
Copy Markdown
Collaborator

ranj063 commented Apr 12, 2019

@xiulipan typo in the commit title. otherwise OK.

@xiulipan xiulipan changed the title ASoC: SOF: soundwire: add init soudwire support ASoC: SOF: soundwire: add init soundwire support Apr 12, 2019
@xiulipan
Copy link
Copy Markdown
Author

@ranj063 Updated. Thanks for checking the typo.

Copy link
Copy Markdown
Collaborator

@kv2019i kv2019i left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code ok, but please fix commit description:

add init soundwire support

Please fix to:

add initial soundwire support

Copy link
Copy Markdown
Member

@plbossart plbossart left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't agree that adding a new DAI type is a minor revision, an old kernel would break functionality by ignoring functionality.

@xiulipan
Copy link
Copy Markdown
Author

@plbossart Then we should revert the thesofproject/sof#1244 first
before we have a final decision about this blocking regression issue caused by ABI.

Revert PR: thesofproject/sof#1262

Add soundwire dai type and update ABI version.

Signed-off-by: Pan Xiuli <xiuli.pan@linux.intel.com>
@plbossart plbossart merged commit 9086043 into thesofproject:topic/sof-dev Apr 17, 2019
@xiulipan xiulipan deleted the pr/abi35 branch April 17, 2019 21:25
plbossart pushed a commit that referenced this pull request Apr 17, 2020
If KVM wasn't used at all before we crash the cleanup procedure fails with
 BUG: unable to handle page fault for address: ffffffffffffffc8
 #PF: supervisor read access in kernel mode
 #PF: error_code(0x0000) - not-present page
 PGD 23215067 P4D 23215067 PUD 23217067 PMD 0
 Oops: 0000 [#8] SMP PTI
 CPU: 0 PID: 3542 Comm: bash Kdump: loaded Tainted: G      D           5.6.0-rc2+ #823
 RIP: 0010:crash_vmclear_local_loaded_vmcss.cold+0x19/0x51 [kvm_intel]

The root cause is that loaded_vmcss_on_cpu list is not yet initialized,
we initialize it in hardware_enable() but this only happens when we start
a VM.

Previously, we used to have a bitmap with enabled CPUs and that was
preventing [masking] the issue.

Initialized loaded_vmcss_on_cpu list earlier, right before we assign
crash_vmclear_loaded_vmcss pointer. blocked_vcpu_on_cpu list and
blocked_vcpu_on_cpu_lock are moved altogether for consistency.

Fixes: 31603d4 ("KVM: VMX: Always VMCLEAR in-use VMCSes during crash with kexec support")
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <20200401081348.1345307-1-vkuznets@redhat.com>
Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
cujomalainey pushed a commit to cujomalainey/linux that referenced this pull request Apr 23, 2020
commit dbef280 upstream.

If KVM wasn't used at all before we crash the cleanup procedure fails with
 BUG: unable to handle page fault for address: ffffffffffffffc8
 #PF: supervisor read access in kernel mode
 #PF: error_code(0x0000) - not-present page
 PGD 23215067 P4D 23215067 PUD 23217067 PMD 0
 Oops: 0000 [thesofproject#8] SMP PTI
 CPU: 0 PID: 3542 Comm: bash Kdump: loaded Tainted: G      D           5.6.0-rc2+ thesofproject#823
 RIP: 0010:crash_vmclear_local_loaded_vmcss.cold+0x19/0x51 [kvm_intel]

The root cause is that loaded_vmcss_on_cpu list is not yet initialized,
we initialize it in hardware_enable() but this only happens when we start
a VM.

Previously, we used to have a bitmap with enabled CPUs and that was
preventing [masking] the issue.

Initialized loaded_vmcss_on_cpu list earlier, right before we assign
crash_vmclear_loaded_vmcss pointer. blocked_vcpu_on_cpu list and
blocked_vcpu_on_cpu_lock are moved altogether for consistency.

Fixes: 31603d4 ("KVM: VMX: Always VMCLEAR in-use VMCSes during crash with kexec support")
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Message-Id: <20200401081348.1345307-1-vkuznets@redhat.com>
Reviewed-by: Sean Christopherson <sean.j.christopherson@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] kernel reporting bug when using same major ABI with different minor ABIs

5 participants