From: Tamas K Lengyel <tamas@tklengyel.com>
To: "Petr Beneš" <w1benny@gmail.com>
Cc: xen-devel@lists.xenproject.org, "Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Alexandru Isaila" <aisaila@bitdefender.com>,
"Petre Pircalabu" <ppircalabu@bitdefender.com>
Subject: Re: [PATCH for-4.19? v3 4/6] x86: Make the maximum number of altp2m views configurable
Date: Fri, 17 May 2024 21:17:56 -0400 [thread overview]
Message-ID: <CABfawhmB+XND75WPJ_MjORyjUiV_h_NNmJQx2BaZ5WRmzkX79A@mail.gmail.com> (raw)
In-Reply-To: <b6bf7e5ba0deab4550b9d15c327015fe7d94d463.1715858136.git.w1benny@gmail.com>
> - ap2m = array_access_nospec(d->arch.altp2m_p2m, altp2m_idx);
> + ap2m = d->arch.altp2m_p2m[altp2m_idx];
Why is it no longer necessary to use array_access_nospec?
Tamas
next prev parent reply other threads:[~2024-05-18 1:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 11:28 [PATCH for-4.19? v3 0/6] x86: Make MAX_ALTP2M configurable Petr Beneš
2024-05-16 11:28 ` [PATCH for-4.19? v3 1/6] x86/p2m: Add braces for better code clarity Petr Beneš
2024-05-16 11:28 ` [PATCH for-4.19? v3 2/6] tools/xl: Add altp2m_count parameter Petr Beneš
2024-05-16 11:28 ` [PATCH for-4.19? v3 3/6] docs/man: Add altp2m_count parameter to the xl.cfg manual Petr Beneš
2024-05-16 11:28 ` [PATCH for-4.19? v3 4/6] x86: Make the maximum number of altp2m views configurable Petr Beneš
2024-05-18 1:17 ` Tamas K Lengyel [this message]
2024-05-18 10:17 ` Petr Beneš
2024-05-16 11:28 ` [PATCH for-4.19? v3 5/6] tools/libxl: Activate the altp2m_count feature Petr Beneš
2024-05-16 11:28 ` [PATCH for-4.19? v3 6/6] tools/ocaml: Add altp2m_count parameter Petr Beneš
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=CABfawhmB+XND75WPJ_MjORyjUiV_h_NNmJQx2BaZ5WRmzkX79A@mail.gmail.com \
--to=tamas@tklengyel.com \
--cc=aisaila@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=ppircalabu@bitdefender.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=w1benny@gmail.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).