From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
ian.jackson@eu.citrix.com, tim@xen.org, julien.grall@arm.com
Subject: Re: [PATCH 2/2] xen: add update indicator to vcpu_runstate_info
Date: Fri, 20 May 2016 17:54:45 +0200 [thread overview]
Message-ID: <573F3345.5010909@suse.com> (raw)
In-Reply-To: <573F4B2F02000078000ED513@suse.com>
On 20/05/16 17:36, Jan Beulich wrote:
>>>> On 20.05.16 at 17:04, <JGross@suse.com> wrote:
>> On 20/05/16 16:49, Jan Beulich wrote:
>>>>>> On 20.05.16 at 15:22, <JGross@suse.com> wrote:
>>>> if ( guest_handle_is_null(runstate_guest(v)) )
>>>> return 1;
>>>>
>>>> + update_flag = VM_ASSIST(v->domain, runstate_update_flag);
>>>> +
>>>> smap_policy = smap_policy_change(v, SMAP_CHECK_ENABLED);
>>>>
>>>> + if ( update_flag )
>>>> + {
>>>> + off = offsetof(struct vcpu_runstate_info, state_entry_time) + 7;
>>>
>>> How come this is outside the following if()? Also sizeof(...) - 1 please
>>> instead of the literal 7.
>>
>> I'm using off for the source address in __raw_copy_to_guest(), too.
>
> But the offset should, afaict, be different for 32-bit (x86) and
> 64-bit (or ARM).
Why? The offset is applied to v->runstate which clearly is the same
for 32 and 64 bit domains, as it is the hypervisor private structure.
Different offsets have to be applied at the destination side only, and
this is done properly (at least I think so).
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-20 15:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 13:22 [PATCH 0/2] Support consistent reads of mapped vcpu_runstate_info Juergen Gross
2016-05-20 13:22 ` [PATCH 1/2] xen/arm: add support for vm_assist hypercall Juergen Gross
2016-05-20 13:58 ` Julien Grall
2016-05-20 14:34 ` Jan Beulich
[not found] ` <573F3C9702000078000ED477@suse.com>
2016-05-20 14:42 ` Juergen Gross
2016-05-20 14:51 ` Jan Beulich
[not found] ` <573F409702000078000ED4C9@suse.com>
2016-05-20 15:08 ` Juergen Gross
2016-05-20 15:33 ` Jan Beulich
[not found] ` <573F4A7302000078000ED510@suse.com>
2016-05-20 16:02 ` Juergen Gross
2016-05-21 13:27 ` Stefano Stabellini
2016-05-21 13:59 ` Julien Grall
2016-05-21 14:03 ` Stefano Stabellini
2016-05-20 13:22 ` [PATCH 2/2] xen: add update indicator to vcpu_runstate_info Juergen Gross
2016-05-20 13:34 ` Andrew Cooper
2016-05-20 13:38 ` Juergen Gross
2016-05-20 14:49 ` Jan Beulich
[not found] ` <573F402602000078000ED4AD@suse.com>
2016-05-20 15:04 ` Juergen Gross
2016-05-20 15:36 ` Jan Beulich
[not found] ` <573F4B2F02000078000ED513@suse.com>
2016-05-20 15:54 ` Juergen Gross [this message]
2016-05-20 16:16 ` Jan Beulich
2016-05-21 14:00 ` Stefano Stabellini
[not found] ` <573F549602000078000ED57C@suse.com>
2016-05-21 4:50 ` Juergen Gross
2016-05-20 14:10 ` [PATCH 0/2] Support consistent reads of mapped vcpu_runstate_info Julien Grall
2016-05-20 14:19 ` Juergen Gross
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=573F3345.5010909@suse.com \
--to=jgross@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).