From: Wei Liu <wei.liu@kernel.org>
To: Jinank Jain <jinankjain@linux.microsoft.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
arnd@arndb.de, peterz@infradead.org, jpoimboe@kernel.org,
seanjc@google.com, kirill.shutemov@linux.intel.com,
ak@linux.intel.com, sathyanarayanan.kuppuswamy@linux.intel.com,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [PATCH 6/6] hv, mshv : Change interrupt vector for nested root partition
Date: Wed, 2 Nov 2022 15:46:31 +0000 [thread overview]
Message-ID: <Y2KQ1w5GOd/PcN61@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <22b6428cc90efb4ed970d61249c877b373a7002a.1667394408.git.jinankjain@microsoft.com>
On Wed, Nov 02, 2022 at 02:00:17PM +0000, Jinank Jain wrote:
> Traditionally we have been using the HYPERVISOR_CALLBACK_VECTOR to relay
> the VMBus interrupt. But this does not work in case of nested
> hypervisor. Microsoft Hypervisor reserves 0x31 to 0x34 as the interrupt
> vector range for VMBus and thus we have to use one of the vectors from
> that range and setup the IDT accordingly.
>
> Signed-off-by: Jinank Jain <jinankjain@linux.microsoft.com>
> ---
> arch/x86/include/asm/idtentry.h | 2 ++
> arch/x86/include/asm/irq_vectors.h | 6 ++++++
[...]
> #if IS_ENABLED(CONFIG_ACRN_GUEST)
> diff --git a/arch/x86/include/asm/irq_vectors.h b/arch/x86/include/asm/irq_vectors.h
> index 43dcb9284208..729d19eab7f5 100644
> --- a/arch/x86/include/asm/irq_vectors.h
> +++ b/arch/x86/include/asm/irq_vectors.h
> @@ -102,6 +102,12 @@
> #if IS_ENABLED(CONFIG_HYPERV)
> #define HYPERV_REENLIGHTENMENT_VECTOR 0xee
> #define HYPERV_STIMER0_VECTOR 0xed
> +/*
> + * FIXME: Change this, once Microsoft Hypervisor changes its assumption
> + * around VMBus interrupt vector allocation for nested root partition.
> + * Or provides a better interface to detect this instead of hardcoding.
> + */
> +#define HYPERV_INTR_NESTED_VMBUS_VECTOR 0x31
I would like to hear x86 maintainers opinion on this.
Thanks,
Wei.
next prev parent reply other threads:[~2022-11-02 15:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 14:00 [PATCH 0/6] Add support running nested Microsoft Hypervisor Jinank Jain
2022-11-02 14:00 ` [PATCH 1/6] mshv: Add support for detecting nested hypervisor Jinank Jain
2022-11-02 14:00 ` [PATCH 2/6] hv: Setup synic registers in case of nested root partition Jinank Jain
2022-11-02 14:58 ` Vitaly Kuznetsov
2022-11-02 14:00 ` [PATCH 3/6] hv: Set the correct EOM register in case of nested hypervisor Jinank Jain
2022-11-02 14:00 ` [PATCH 4/6] hv: Add an interface to do nested hypercalls Jinank Jain
2022-11-02 14:00 ` [PATCH 5/6] hv: Enable vmbus driver for nested root partition Jinank Jain
2022-11-02 14:00 ` [PATCH 6/6] hv, mshv : Change interrupt vector " Jinank Jain
2022-11-02 15:46 ` Wei Liu [this message]
2022-11-24 5:53 ` [PATCH v5 0/5] Add support running nested Microsoft Hypervisor Jinank Jain
2022-11-24 5:53 ` [PATCH v5 1/5] x86/hyperv: Add support for detecting nested hypervisor Jinank Jain
2022-11-24 5:53 ` [PATCH v5 2/5] Drivers: hv: Setup synic registers in case of nested root partition Jinank Jain
2022-11-24 5:53 ` [PATCH v5 3/5] x86/hyperv: Add an interface to do nested hypercalls Jinank Jain
2022-11-24 5:53 ` [PATCH v5 4/5] Drivers: hv: Enable vmbus driver for nested root partition Jinank Jain
2022-11-24 5:53 ` [PATCH v5 5/5] x86/hyperv: Change interrupt vector " Jinank Jain
2022-11-24 6:01 ` [PATCH v5 0/5] Add support running nested Microsoft Hypervisor Jinank Jain
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=Y2KQ1w5GOd/PcN61@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=ak@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=jinankjain@linux.microsoft.com \
--cc=jpoimboe@kernel.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=kys@microsoft.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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