From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: andre.przywara@arm.com, nd@arm.com, punit.agrawal@arm.com,
xen-devel@lists.xen.org
Subject: Re: [PATCH 3/3] xen/arm: p2m: Perform local TLB invalidation on vCPU migration
Date: Tue, 14 Mar 2017 23:23:15 +0000 [thread overview]
Message-ID: <e45b9826-978e-fc5b-aa4d-c0556859595a@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1703141535530.4807@sstabellini-ThinkPad-X260>
Hi Stefano,
On 03/14/2017 10:39 PM, Stefano Stabellini wrote:
> On Wed, 8 Mar 2017, Julien Grall wrote:
>> On 08/03/2017 19:48, Stefano Stabellini wrote:
>>> On Wed, 8 Mar 2017, Julien Grall wrote:
> I see your point, it is a good idea to use the remaining space in struct
> domain. The only issue is that a user could set CONFIG_NR_CPUS large
> enough to push last_vcpu_ran beyond the page boundary. I think we need
> to add a BUILD_BUG_ON(sizeof(struct domain) >= PAGE_SIZE).
There is already a BUILD_BUG_ON(sizeof(struct domain) > PAGE_SIZE) in
alloc_domain_struct. Would it be enough for you?
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-14 23:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 18:05 [PATCH 0/3] xen/arm: p2m: Perform local invalidation on vCPU migration Julien Grall
2017-03-08 18:06 ` [PATCH 1/3] xen/arm: hvm_domain does not need to be cacheline aligned Julien Grall
2017-03-08 18:30 ` Stefano Stabellini
2017-03-08 18:06 ` [PATCH 2/3] xen/arm: Introduce INVALID_VCPU_ID Julien Grall
2017-03-08 18:31 ` Stefano Stabellini
2017-03-08 18:06 ` [PATCH 3/3] xen/arm: p2m: Perform local TLB invalidation on vCPU migration Julien Grall
2017-03-08 18:58 ` Stefano Stabellini
2017-03-08 19:27 ` Julien Grall
2017-03-08 19:48 ` Stefano Stabellini
2017-03-08 21:37 ` Julien Grall
2017-03-14 22:39 ` Stefano Stabellini
2017-03-14 23:23 ` Julien Grall [this message]
2017-03-14 23:29 ` Stefano Stabellini
2017-03-08 21:37 ` Julien Grall
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=e45b9826-978e-fc5b-aa4d-c0556859595a@arm.com \
--to=julien.grall@arm.com \
--cc=andre.przywara@arm.com \
--cc=nd@arm.com \
--cc=punit.agrawal@arm.com \
--cc=sstabellini@kernel.org \
--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).