public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Kisel <romank@linux.microsoft.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: ardb@kernel.org, bp@alien8.de, brgerst@gmail.com,
	dave.hansen@linux.intel.com, decui@microsoft.com,
	dimitri.sivanich@hpe.com, gautham.shenoy@amd.com,
	haiyangz@microsoft.com, hpa@zytor.com, imran.f.khan@oracle.com,
	jacob.jun.pan@linux.intel.com, jpoimboe@kernel.org,
	justin.ernst@hpe.com, kprateek.nayak@amd.com, kyle.meyer@hpe.com,
	kys@microsoft.com, lenb@kernel.org, mhklinux@outlook.com,
	mingo@redhat.com, nikunj@amd.com, papaluri@amd.com,
	patryk.wlazlyn@linux.intel.com, peterz@infradead.org,
	rafael@kernel.org, russ.anderson@hpe.com, sohil.mehta@intel.com,
	steve.wahl@hpe.com, tglx@linutronix.de, thomas.lendacky@amd.com,
	tiala@microsoft.com, yuehaibing@huawei.com,
	linux-acpi@vger.kernel.org, linux-hyperv@vger.kernel.org,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	apais@microsoft.com, benhill@microsoft.com,
	bperkins@microsoft.com, sunilmut@microsoft.com
Subject: Re: [PATCH hyperv-next 0/2] arch/x86, x86/hyperv: Few fixes for the AP startup
Date: Thu, 8 May 2025 12:43:00 -0700	[thread overview]
Message-ID: <7e9dc568-c685-4530-b2b8-669a58adc3fc@linux.microsoft.com> (raw)
In-Reply-To: <aBz6Vuv9w4uRjaG_@liuwe-devbox-ubuntu-v2.tail21d00.ts.net>



On 5/8/2025 11:39 AM, Wei Liu wrote:
> On Wed, May 07, 2025 at 11:22:24AM -0700, Roman Kisel wrote:
>> This patchset combines two patches that depend on each other and were not applying
>> cleanly:
>>    1. Fix APIC ID and VP index confusion in hv_snp_boot_ap():
>>      https://lore.kernel.org/linux-hyperv/20250430204720.108962-1-romank@linux.microsoft.com/
>>    2. Provide the CPU number in the wakeup AP callback:
>>      https://lore.kernel.org/linux-hyperv/20250430204720.108962-1-romank@linux.microsoft.com/
>>
>> I rebased the patches on top of the latest hyperv-next tree and updated the second patch
>> that broke the linux-next build. That fix that, I made one non-functional change:
>> updated the signature of numachip_wakeup_secondary() to match the parameter list of
>> wakeup_secondary_cpu().
>>
>> Roman Kisel (2):
>>    x86/hyperv: Fix APIC ID and VP index confusion in hv_snp_boot_ap()
>>    arch/x86: Provide the CPU number in the wakeup AP callback
> 
> I queue these up.
> 
> Just so you know I'm experimenting a new setup. These have been applied
> to hyperv-next-staging. It will take some time for them to propagate to
> hyperv-next.

Thank you very much! That's exciting news about the new staging setup!!

> 
> Thanks,
> Wei.
> 
>>
>>   arch/x86/coco/sev/core.c             | 13 ++-----
>>   arch/x86/hyperv/hv_init.c            | 33 +++++++++++++++++
>>   arch/x86/hyperv/hv_vtl.c             | 54 ++++------------------------
>>   arch/x86/hyperv/ivm.c                | 11 ++++--
>>   arch/x86/include/asm/apic.h          |  8 ++---
>>   arch/x86/include/asm/mshyperv.h      |  7 ++--
>>   arch/x86/kernel/acpi/madt_wakeup.c   |  2 +-
>>   arch/x86/kernel/apic/apic_noop.c     |  8 ++++-
>>   arch/x86/kernel/apic/apic_numachip.c |  2 +-
>>   arch/x86/kernel/apic/x2apic_uv_x.c   |  2 +-
>>   arch/x86/kernel/smpboot.c            | 10 +++---
>>   include/hyperv/hvgdk_mini.h          |  2 +-
>>   12 files changed, 76 insertions(+), 76 deletions(-)
>>
>>
>> base-commit: 9b0844d87b1407681b78130429f798beb366f43f
>> -- 
>> 2.43.0
>>

-- 
Thank you,
Roman


      reply	other threads:[~2025-05-08 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 18:22 [PATCH hyperv-next 0/2] arch/x86, x86/hyperv: Few fixes for the AP startup Roman Kisel
2025-05-07 18:22 ` [PATCH hyperv-next 1/2] x86/hyperv: Fix APIC ID and VP index confusion in hv_snp_boot_ap() Roman Kisel
2025-05-07 18:22 ` [PATCH hyperv-next 2/2] arch/x86: Provide the CPU number in the wakeup AP callback Roman Kisel
2025-05-07 20:09   ` Rafael J. Wysocki
2025-05-08  1:10     ` Wei Liu
2025-05-08  4:22 ` [PATCH hyperv-next 0/2] arch/x86, x86/hyperv: Few fixes for the AP startup Michael Kelley
2025-05-08 15:09   ` Roman Kisel
2025-05-08 18:39 ` Wei Liu
2025-05-08 19:43   ` Roman Kisel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7e9dc568-c685-4530-b2b8-669a58adc3fc@linux.microsoft.com \
    --to=romank@linux.microsoft.com \
    --cc=apais@microsoft.com \
    --cc=ardb@kernel.org \
    --cc=benhill@microsoft.com \
    --cc=bp@alien8.de \
    --cc=bperkins@microsoft.com \
    --cc=brgerst@gmail.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=decui@microsoft.com \
    --cc=dimitri.sivanich@hpe.com \
    --cc=gautham.shenoy@amd.com \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=imran.f.khan@oracle.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=jpoimboe@kernel.org \
    --cc=justin.ernst@hpe.com \
    --cc=kprateek.nayak@amd.com \
    --cc=kyle.meyer@hpe.com \
    --cc=kys@microsoft.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhklinux@outlook.com \
    --cc=mingo@redhat.com \
    --cc=nikunj@amd.com \
    --cc=papaluri@amd.com \
    --cc=patryk.wlazlyn@linux.intel.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=russ.anderson@hpe.com \
    --cc=sohil.mehta@intel.com \
    --cc=steve.wahl@hpe.com \
    --cc=sunilmut@microsoft.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tiala@microsoft.com \
    --cc=wei.liu@kernel.org \
    --cc=x86@kernel.org \
    --cc=yuehaibing@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox