From: "Alejandro Vallejo" <alejandro.vallejo@cloud.com>
To: "Jan Beulich" <jbeulich@suse.com>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 12/14] x86/fpu: Pass explicit xsave areas to fpu_(f)xsave()
Date: Tue, 29 Oct 2024 10:59:58 +0000 [thread overview]
Message-ID: <D588KIJCBFQQ.2AC6KE08Z8YWK@cloud.com> (raw)
In-Reply-To: <85e7334b-b878-4896-8f7a-462ba73ea9e2@suse.com>
On Tue Oct 29, 2024 at 8:37 AM GMT, Jan Beulich wrote:
> On 28.10.2024 16:49, Alejandro Vallejo wrote:
> > --- a/xen/arch/x86/xstate.c
> > +++ b/xen/arch/x86/xstate.c
> > @@ -300,9 +300,8 @@ void compress_xsave_states(struct vcpu *v, const void *src, unsigned int size)
> > vcpu_unmap_xsave_area(v, xstate);
> > }
> >
> > -void xsave(struct vcpu *v, uint64_t mask)
> > +void xsave(struct vcpu *v, struct xsave_struct *ptr, uint64_t mask)
> > {
> > - struct xsave_struct *ptr = v->arch.xsave_area;
> > uint32_t hmask = mask >> 32;
> > uint32_t lmask = mask;
> > unsigned int fip_width = v->domain->arch.x87_fip_width;
>
> Imo this change wants to constify v at the same time, to demonstrate that
> nothing is changed through v anymore. The comment may extend to other functions
> as well that are being altered here; I only closely looks at this one.
>
> Jan
I didn't think of that angle... I'll have a look and take it into account for
v2.
Cheers,
Alejandro
next prev parent reply other threads:[~2024-10-29 11:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 15:49 [PATCH 00/14] x86: Address Space Isolation FPU preparations Alejandro Vallejo
2024-10-28 15:49 ` [PATCH 01/14] x86/xstate: Update stale assertions in fpu_x{rstor,save}() Alejandro Vallejo
2024-10-28 17:16 ` Andrew Cooper
2024-10-29 8:13 ` Jan Beulich
2024-10-29 10:56 ` Alejandro Vallejo
2024-10-28 15:49 ` [PATCH 02/14] x86/xstate: Create map/unmap primitives for xsave areas Alejandro Vallejo
2024-10-28 17:20 ` Andrew Cooper
2024-10-29 11:57 ` Alejandro Vallejo
2024-10-29 13:24 ` Frediano Ziglio
2024-10-29 14:23 ` Alejandro Vallejo
2024-10-29 13:28 ` Jan Beulich
2024-10-29 14:12 ` Alejandro Vallejo
2024-10-29 8:19 ` Jan Beulich
2024-10-29 10:55 ` Alejandro Vallejo
2024-10-28 15:49 ` [PATCH 03/14] x86/hvm: Map/unmap xsave area in hvm_save_cpu_ctxt() Alejandro Vallejo
2024-10-28 15:49 ` [PATCH 04/14] x86/fpu: Map/umap xsave area in vcpu_{reset,setup}_fpu() Alejandro Vallejo
2024-10-28 15:49 ` [PATCH 05/14] x86/xstate: Map/unmap xsave area in xstate_set_init() and handle_setbv() Alejandro Vallejo
2024-10-29 8:26 ` Jan Beulich
2024-10-29 13:00 ` Alejandro Vallejo
2024-10-29 13:31 ` Jan Beulich
2024-10-29 14:14 ` Alejandro Vallejo
2024-10-28 15:49 ` [PATCH 06/14] x86/hvm: Map/unmap xsave area in hvmemul_{get,put}_fpu() Alejandro Vallejo
2024-10-29 8:30 ` Jan Beulich
2024-10-28 15:49 ` [PATCH 07/14] x86/domctl: Map/unmap xsave area in arch_get_info_guest() Alejandro Vallejo
2024-10-28 15:49 ` [PATCH 08/14] x86/xstate: Map/unmap xsave area in {compress,expand}_xsave_states() Alejandro Vallejo
2024-10-28 15:49 ` [PATCH 09/14] x86/emulator: Refactor FXSAVE_AREA to use wrappers Alejandro Vallejo
2024-10-28 15:49 ` [PATCH 10/14] x86/mpx: Map/unmap xsave area in in read_bndcfgu() Alejandro Vallejo
2024-10-29 8:27 ` Jan Beulich
2024-10-28 15:49 ` [PATCH 11/14] x86/mpx: Adjust read_bndcfgu() to clean after itself Alejandro Vallejo
2024-10-29 8:32 ` Jan Beulich
2024-10-28 15:49 ` [PATCH 12/14] x86/fpu: Pass explicit xsave areas to fpu_(f)xsave() Alejandro Vallejo
2024-10-29 8:37 ` Jan Beulich
2024-10-29 10:59 ` Alejandro Vallejo [this message]
2024-10-28 15:49 ` [PATCH 13/14] x86/fpu: Pass explicit xsave areas to fpu_(f)xrstor() Alejandro Vallejo
2024-10-29 8:40 ` Jan Beulich
2024-10-28 15:49 ` [PATCH 14/14] x86/xstate: Make xstate_all() and vcpu_xsave_mask() take explicit xstate Alejandro Vallejo
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=D588KIJCBFQQ.2AC6KE08Z8YWK@cloud.com \
--to=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.