From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH 3/3] xen/x86: Rename and simplify async_event_* infrastructure
Date: Tue, 18 Feb 2020 17:31:26 +0100 [thread overview]
Message-ID: <8f3b2686-7d47-3899-2621-a8a45d2bbf02@suse.com> (raw)
In-Reply-To: <20200217111740.7298-4-andrew.cooper3@citrix.com>
On 17.02.2020 12:17, Andrew Cooper wrote:
> --- a/xen/arch/x86/pv/iret.c
> +++ b/xen/arch/x86/pv/iret.c
> @@ -27,15 +27,15 @@ static void async_exception_cleanup(struct vcpu *curr)
> {
> unsigned int trap;
>
> - if ( !curr->arch.async_exception_mask )
> + if ( !curr->arch.async_event_mask )
> return;
>
> - if ( !(curr->arch.async_exception_mask & (curr->arch.async_exception_mask - 1)) )
> - trap = __scanbit(curr->arch.async_exception_mask, VCPU_TRAP_NONE);
> + if ( !(curr->arch.async_event_mask & (curr->arch.async_event_mask - 1)) )
> + trap = __scanbit(curr->arch.async_event_mask, 0);
The transformation just by itself is clearly not "no functional
change"; it is together with the prior if(), but it took me a
little to convince myself. I don't recall why VCPU_TRAP_NONE was
used here originally (possibly just because of it being zero),
but I think the latest now it would be better to use
VCPU_TRAP_LAST + 1 instead, as 0 now has an actual meaning.
> @@ -557,12 +546,22 @@ struct arch_vcpu
>
> struct vpmu_struct vpmu;
>
> - struct {
> - bool pending;
> - uint8_t old_mask;
> - } async_exception_state[VCPU_TRAP_LAST];
> -#define async_exception_state(t) async_exception_state[(t)-1]
> - uint8_t async_exception_mask;
> + union {
> +#define VCPU_TRAP_NMI 0
> +#define VCPU_TRAP_MCE 1
> +#define VCPU_TRAP_LAST VCPU_TRAP_MCE
> + struct {
> + bool pending;
> + uint8_t old_mask;
> + } async_event[VCPU_TRAP_LAST + 1];
> + struct {
> + bool nmi_pending;
> + uint8_t nmi_old_mask;
> + bool mce_pending;
> + uint8_t mce_old_mask;
> + };
> + };
How about
union {
#define VCPU_TRAP_NMI 0
#define VCPU_TRAP_MCE 1
#define VCPU_TRAP_LAST VCPU_TRAP_MCE
struct async_event_state {
bool pending;
uint8_t old_mask;
} async_event[VCPU_TRAP_LAST + 1];
struct {
struct async_event_state nmi;
struct async_event_state mce;
};
};
(structure tag subject to improvement)?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-02-18 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 11:17 [Xen-devel] [PATCH 0/3] xen: async_exception_* cleanup Andrew Cooper
2020-02-17 11:17 ` [Xen-devel] [PATCH 1/3] x86/nmi: Corrections and improvements to do_nmi_stats() Andrew Cooper
2020-02-18 16:07 ` Jan Beulich
2020-02-17 11:17 ` [Xen-devel] [PATCH 2/3] xen: Move async_exception_* infrastructure into x86 Andrew Cooper
2020-02-18 16:11 ` Jan Beulich
2020-02-18 16:23 ` Andrew Cooper
2020-02-17 11:17 ` [Xen-devel] [PATCH 3/3] xen/x86: Rename and simplify async_event_* infrastructure Andrew Cooper
2020-02-18 16:31 ` Jan Beulich [this message]
2020-02-20 18:24 ` Andrew Cooper
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=8f3b2686-7d47-3899-2621-a8a45d2bbf02@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.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 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.