From: Jork Loeser <jloeser@linux.microsoft.com>
To: Michael Kelley <mhklinux@outlook.com>
Cc: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Long Li <longli@microsoft.com>,
Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>, Arnd Bergmann <arnd@arndb.de>,
Anirudh Rayabharam <anirudh@anirudhrb.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: RE: [PATCH v4 1/3] mshv: limit SynIC management to MSHV-owned resources
Date: Tue, 5 May 2026 04:35:46 -0700 (PDT) [thread overview]
Message-ID: <91faacb-d16-8540-4713-dad25bacf695@linux.microsoft.com> (raw)
In-Reply-To: <SN6PR02MB4157280E305E11C5840B444DD4312@SN6PR02MB4157.namprd02.prod.outlook.com>
On Mon, 4 May 2026, Michael Kelley wrote:
> From: Jork Loeser <jloeser@linux.microsoft.com> Sent: Monday, April 27, 2026 2:39 PM
>>
>> While here, fix the SIEFP and SIRBP memremap() and virt_to_phys()
>> calls to use HV_HYP_PAGE_SHIFT/HV_HYP_PAGE_SIZE instead of
>> PAGE_SHIFT/PAGE_SIZE. The hypervisor always uses 4K pages for SynIC
>> register GPAs regardless of the kernel page size, so using PAGE_SHIFT
>> produces wrong addresses on ARM64 with 64K pages.
>
> I agree that this is a good change. But any kernel image built with
> CONFIG_MSHV_ROOT set must use only 4KiB pages, as enforced
> by the dependency in drivers/hv/Kconfig. The change makes the
> code explicitly match the SynIC register layout, which is good,
> but it doesn't actually fix a problem since root MSHV code can't
> run on ARM64 with 64KiB pages. My only concern is that this
> commit message should not imply that an ARM64/64KiB
> configuration is possible for the root.
Agree for root. For L1VH, I think it theoretically could (likely with
other changes needing to happen elsewhere).
Best,
Jork
next prev parent reply other threads:[~2026-05-05 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 21:38 [PATCH v4 0/3] Hyper-V: kexec fixes for L1VH (mshv) Jork Loeser
2026-04-27 21:38 ` [PATCH v4 1/3] mshv: limit SynIC management to MSHV-owned resources Jork Loeser
2026-04-28 23:27 ` Stanislav Kinsburskii
2026-04-29 9:58 ` Anirudh Rayabharam
2026-05-04 15:09 ` Michael Kelley
2026-05-05 11:35 ` Jork Loeser [this message]
2026-04-27 21:38 ` [PATCH v4 2/3] mshv: clean up SynIC state on kexec for L1VH Jork Loeser
2026-04-28 23:28 ` Stanislav Kinsburskii
2026-04-29 9:58 ` Anirudh Rayabharam
2026-04-27 21:38 ` [PATCH v4 3/3] mshv: unmap debugfs stats pages on kexec Jork Loeser
2026-04-28 23:31 ` Stanislav Kinsburskii
2026-04-29 10:10 ` Anirudh Rayabharam
2026-04-29 22:57 ` [PATCH v4 0/3] Hyper-V: kexec fixes for L1VH (mshv) Wei Liu
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=91faacb-d16-8540-4713-dad25bacf695@linux.microsoft.com \
--to=jloeser@linux.microsoft.com \
--cc=anirudh@anirudhrb.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=kys@microsoft.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mhklinux@outlook.com \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=wei.liu@kernel.org \
--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