From: Juergen Gross <jgross@suse.com>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: sergey.dyasli@citrix.com, Wei Liu <wei.liu2@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
tim@xen.org, xen-devel@lists.xen.org,
Jan Beulich <JBeulich@suse.com>,
security@xen.org, dfaggioli@suse.com, dwmw@amazon.co.uk,
roger.pau@citrix.com
Subject: Re: L1TF, and future work
Date: Sat, 25 Aug 2018 07:21:33 +0200 [thread overview]
Message-ID: <c8c0d4ad-171b-b28f-97b1-77018f3a99ad@suse.com> (raw)
In-Reply-To: <CAKf6xpudQ5dmheXAAEPm_bJ=n7YJPwBuUHQbS2_45bqKWM8ZEA@mail.gmail.com>
On 24/08/18 20:43, Jason Andryuk wrote:
> On Wed, Aug 15, 2018 at 10:39 AM Juergen Gross <jgross@suse.com> wrote:
>>
>> On 15/08/18 16:10, Jan Beulich wrote:
>>>>>> On 15.08.18 at 15:17, <andrew.cooper3@citrix.com> wrote:
>>>> 2) 32bit PV guests which use writeable pagetable support will
>>>> automatically get shadowed when the clear the lower half.
>>>
>>> ... of a page table entry.
>>>
>>>> Ideally, such
>>>> guests should be modified to use hypercalls rather than the ptwr
>>>> infrastructure (as its more efficient to begin with), but we can
>>>> probably work around this in Xen by emulating the next few instructions
>>>> until we have a complete PTE (same as the shadow code).
>>>
>>> Provided the intervening insns are simple enough. I've looked into
>>> current Linux pv-ops code the other day, and afaict it's already
>>> using mmu-op or cmpxchg8b, but not two separate mov-s. But
>>> of course I've looked at the general routines only, not at things
>>> perhaps hidden in special cases, or in init-only code.
>>
>> Look at xen_pte_clear(). Inside irq handling it will use (PAE case):
>>
>> static inline void native_pte_clear(struct mm_struct *mm, unsigned long
>> addr,
>> pte_t *ptep)
>> {
>> ptep->pte_low = 0;
>> smp_wmb();
>> ptep->pte_high = 0;
>> }
>
> I've been testing out set_64bit for PTE operations on 32bit PAE. I
> haven't found all the spots, but shadowing is now enabled a few
> seconds into boot instead of immediately.
>
> And yes, I think https://bugzilla.kernel.org/show_bug.cgi?id=198497 is
> related as you presumed a while back.
I have a patch series (two patches) avoiding shadowing completely:
https://lists.xen.org/archives/html/xen-devel/2018-08/msg01785.html
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-08-25 5:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 13:17 L1TF, and future work Andrew Cooper
2018-08-15 13:21 ` Andrew Cooper
2018-08-15 14:11 ` Juergen Gross
2018-08-15 14:10 ` Jan Beulich
[not found] ` <5B74347002000078001DE714@suse.com>
2018-08-15 14:35 ` Juergen Gross
2018-08-24 18:43 ` Jason Andryuk
2018-08-25 5:21 ` Juergen Gross [this message]
2018-08-27 12:10 ` Jason Andryuk
2018-08-24 9:15 ` Dario Faggioli
2018-09-10 21:45 ` Tamas K Lengyel
2018-09-11 15:13 ` Dario Faggioli
2018-09-11 17:14 ` Tamas K Lengyel
2018-09-12 6:12 ` Dario Faggioli
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=c8c0d4ad-171b-b28f-97b1-77018f3a99ad@suse.com \
--to=jgross@suse.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dfaggioli@suse.com \
--cc=dwmw@amazon.co.uk \
--cc=jandryuk@gmail.com \
--cc=roger.pau@citrix.com \
--cc=security@xen.org \
--cc=sergey.dyasli@citrix.com \
--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).