From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Cc: Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 1/2] x86/hvm: fix arch_set_info_hvm_guest SEG macro
Date: Wed, 9 Aug 2017 11:19:55 +0100 [thread overview]
Message-ID: <d3f82246-464c-b07c-4eb5-f23c40671723@citrix.com> (raw)
In-Reply-To: <20170809101821.50836-1-roger.pau@citrix.com>
On 09/08/17 11:18, Roger Pau Monne wrote:
> Commit 6c9abf modified the SEG macro in arch_set_info_hvm_guest and
> inverted the limit and base fields. Restore the correct order.
>
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
Sorry for breaking things!
> ---
> Cc: Jan Beulich <jbeulich@suse.com>
> Cc: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> xen/arch/x86/hvm/domain.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/xen/arch/x86/hvm/domain.c b/xen/arch/x86/hvm/domain.c
> index 7e11541089..60474649de 100644
> --- a/xen/arch/x86/hvm/domain.c
> +++ b/xen/arch/x86/hvm/domain.c
> @@ -137,7 +137,7 @@ int arch_set_info_hvm_guest(struct vcpu *v, const vcpu_hvm_context_t *ctx)
>
> #define SEG(s, r) ({ \
> s = (struct segment_register) \
> - { 0, { (r)->s ## _ar }, (r)->s ## _base, (r)->s ## _limit }; \
> + { 0, { (r)->s ## _ar }, (r)->s ## _limit, (r)->s ## _base }; \
> /* Set accessed / busy bit for present segments. */ \
> if ( s.p ) \
> s.type |= (x86_seg_##s != x86_seg_tr ? 1 : 2); \
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-08-09 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 10:18 [PATCH 1/2] x86/hvm: fix arch_set_info_hvm_guest SEG macro Roger Pau Monne
2017-08-09 10:18 ` [PATCH 2/2] x86: fix printed messages in arch_set_info_hvm_guest Roger Pau Monne
2017-08-09 10:23 ` Andrew Cooper
2017-08-09 10:19 ` Andrew Cooper [this message]
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=d3f82246-464c-b07c-4eb5-f23c40671723@citrix.com \
--to=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 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).