From: Julien Grall <julien.grall@arm.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: sstabellini@kernel.org, wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: [for-4.7] xen/arm: Force broadcast of TLB and instruction cache maintenance instructions
Date: Tue, 26 Apr 2016 10:36:49 +0100 [thread overview]
Message-ID: <571F36B1.5010002@arm.com> (raw)
In-Reply-To: <20160425182208.GA13411@char.us.oracle.com>
Hi Konrad,
On 25/04/2016 19:22, Konrad Rzeszutek Wilk wrote:
> On Mon, Apr 18, 2016 at 10:29:51AM +0100, Julien Grall wrote:
>> UP guest usually uses TLB instruction to flush only on the local CPU. The
>> TLB flush won't be broadcasted across all the CPUs within the same
>> innershareable domain.
>>
>> When the vCPU is migrated between different CPUs, it may be rescheduled
>> to a previous CPU where the TLB has not been flushed. The TLB may
>> contain stale entries which will result to translate incorrectly a VA to
>> IPA or even cause TLB conflicts.
>>
>> To avoid a such situation, always set HCR_EL2.FB which will force the
>> broadcast of TLB and instruction cache maintenance instructions.
>> Cheers,
>>
>> Signed-off-by: Julien Grall <julien.grall@arm.com>
> I presume this needs an Release-Ack ?
That's right. I would also like to have an acked-by/reviewed-by from
Stefano as he was concerned about the performance impact of this patch.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-04-26 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 9:29 [for-4.7] xen/arm: Force broadcast of TLB and instruction cache maintenance instructions Julien Grall
2016-04-25 10:45 ` Stefano Stabellini
2016-04-25 13:54 ` Julien Grall
2016-04-26 9:45 ` Stefano Stabellini
2016-04-27 10:26 ` Julien Grall
2016-04-25 18:22 ` Konrad Rzeszutek Wilk
2016-04-26 9:36 ` Julien Grall [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=571F36B1.5010002@arm.com \
--to=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=sstabellini@kernel.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 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.