From: Julien Grall <julien@xen.org>
To: "haseeb.ashraf@siemens.com" <haseeb.ashraf@siemens.com>,
Mohamed Mediouni <mohamed@unpredictable.fr>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"Volodymyr_Babchuk@epam.com" <Volodymyr_Babchuk@epam.com>,
"Driscoll, Dan" <dan.driscoll@siemens.com>,
"Bachtel, Andrew" <andrew.bachtel@siemens.com>,
"fahad.arslan@siemens.com" <fahad.arslan@siemens.com>,
"noor.ahsan@siemens.com" <noor.ahsan@siemens.com>,
"brian.sheppard@siemens.com" <brian.sheppard@siemens.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Bertrand Marquis <Bertrand.Marquis@arm.com>,
Michal Orzel <michal.orzel@amd.com>
Subject: Re: Limitations for Running Xen on KVM Arm64
Date: Wed, 5 Nov 2025 17:44:18 +0000 [thread overview]
Message-ID: <1a4490d7-5fb5-44a0-bd77-c8e0548a2553@xen.org> (raw)
In-Reply-To: <KL1PR0601MB458825063113CD4CB2F9440FE6C5A@KL1PR0601MB4588.apcprd06.prod.outlook.com>
On 05/11/2025 13:39, haseeb.ashraf@siemens.com wrote:
> Hi,
Hi Haseeb,
> I have sent out a patch using IPAS2E1IS. The R version RIPAS2E1IS would only be helpful if we have to invalidate more than one page at a time and this is not possible unless a batch version of hypercall is implemented because otherwise there is only one page removed per hypercall.
I have only briefly look at your patch. You have the following loop:
/* Invalidate stage-2 TLB entries by IPA range */
for ( i = 0; i < page_count; i++ ) {
flush_guest_tlb_one_s2(ipa);
ipa += 1UL << PAGE_SHIFT;
}
With RIPAS2E1IS, you would be able to replace this loop with a single
instruction. This may not have any value in your setup because you are
unmaping 4KB at the time. But there are other hypercalls (such as
XENMEM_decrease_reservation) where you can remove larger mapping.
So I think there are some values to use the range version. Although, I
would be fine if this is not handled in your current patch.
> Thanks again for your great suggestions. Please review my patch, you should've received an email.
I will add it in my list of reviews.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2025-11-05 17:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 6:12 Limitations for Running Xen on KVM Arm64 haseeb.ashraf
2025-10-30 13:41 ` haseeb.ashraf
2025-10-30 18:33 ` Mohamed Mediouni
2025-10-30 23:55 ` Julien Grall
2025-10-31 0:20 ` Mohamed Mediouni
2025-10-31 0:38 ` Mohamed Mediouni
2025-10-31 9:18 ` Julien Grall
2025-10-31 11:54 ` Mohamed Mediouni
2025-11-01 17:20 ` Julien Grall
2025-10-31 13:01 ` haseeb.ashraf
2025-11-01 18:23 ` Julien Grall
2025-11-03 13:09 ` haseeb.ashraf
2025-11-03 14:30 ` Julien Grall
2025-11-04 7:50 ` haseeb.ashraf
2025-11-05 13:39 ` haseeb.ashraf
2025-11-05 17:44 ` Julien Grall [this message]
2025-10-31 15:17 ` Mohamed Mediouni
2025-11-01 2:04 ` Demi Marie Obenour
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=1a4490d7-5fb5-44a0-bd77-c8e0548a2553@xen.org \
--to=julien@xen.org \
--cc=Bertrand.Marquis@arm.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.bachtel@siemens.com \
--cc=brian.sheppard@siemens.com \
--cc=dan.driscoll@siemens.com \
--cc=fahad.arslan@siemens.com \
--cc=haseeb.ashraf@siemens.com \
--cc=michal.orzel@amd.com \
--cc=mohamed@unpredictable.fr \
--cc=noor.ahsan@siemens.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).