From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, Tim Deegan <tim@xen.org>,
George Dunlap <george.dunlap@citrix.com>, Wei Liu <wl@xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH v9 1/3] x86/tlb: introduce a flush HVM ASIDs flag
Date: Tue, 14 Apr 2020 09:52:45 +0200 [thread overview]
Message-ID: <20200414075245.GC28601@Air-de-Roger> (raw)
In-Reply-To: <30062a0c-6587-a16e-2b31-de0dd6bf4c9a@suse.com>
On Thu, Apr 09, 2020 at 01:54:40PM +0200, Jan Beulich wrote:
> On 06.04.2020 12:57, Roger Pau Monne wrote:
> > --- a/xen/arch/x86/mm/hap/hap.c
> > +++ b/xen/arch/x86/mm/hap/hap.c
> > @@ -118,7 +118,7 @@ int hap_track_dirty_vram(struct domain *d,
> > p2m_change_type_range(d, begin_pfn, begin_pfn + nr,
> > p2m_ram_rw, p2m_ram_logdirty);
> >
> > - flush_tlb_mask(d->dirty_cpumask);
> > + hap_flush_tlb_mask(d->dirty_cpumask);
> >
> > memset(dirty_bitmap, 0xff, size); /* consider all pages dirty */
> > }
> > @@ -205,7 +205,7 @@ static int hap_enable_log_dirty(struct domain *d, bool_t log_global)
> > * to be read-only, or via hardware-assisted log-dirty.
> > */
> > p2m_change_entry_type_global(d, p2m_ram_rw, p2m_ram_logdirty);
> > - flush_tlb_mask(d->dirty_cpumask);
> > + hap_flush_tlb_mask(d->dirty_cpumask);
> > }
> > return 0;
> > }
> > @@ -234,7 +234,7 @@ static void hap_clean_dirty_bitmap(struct domain *d)
> > * be read-only, or via hardware-assisted log-dirty.
> > */
> > p2m_change_entry_type_global(d, p2m_ram_rw, p2m_ram_logdirty);
> > - flush_tlb_mask(d->dirty_cpumask);
> > + hap_flush_tlb_mask(d->dirty_cpumask);
> > }
> >
> > /************************************************/
> > @@ -798,7 +798,7 @@ hap_write_p2m_entry(struct p2m_domain *p2m, unsigned long gfn, l1_pgentry_t *p,
> >
> > safe_write_pte(p, new);
> > if ( old_flags & _PAGE_PRESENT )
> > - flush_tlb_mask(d->dirty_cpumask);
> > + hap_flush_tlb_mask(d->dirty_cpumask);
> >
> > paging_unlock(d);
> >
>
> Following up on my earlier mail about paging_log_dirty_range(), I'm
> now of the opinion that all of these flushes should go away too. I
> can only assume that they got put where they are when HAP code was
> cloned from the shadow one. These are only p2m operations, and hence
> p2m level TLB flushing is all that's needed here.
IIRC without those ASID flushes NPT won't work correctly, as I think
it relies on those flushes when updating the p2m.
We could see about moving those flushes inside the NPT functions that
modify the p2m, AFAICT p2m_pt_set_entry which calls
p2m->write_p2m_entry relies on the later doing the ASID flushes, as it
doesn't perform any.
Thanks, Roger.
next prev parent reply other threads:[~2020-04-14 7:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 10:57 [PATCH v9 0/3] x86/guest: use assisted TLB flush in guest mode Roger Pau Monne
2020-04-06 10:57 ` [PATCH v9 1/3] x86/tlb: introduce a flush HVM ASIDs flag Roger Pau Monne
2020-04-08 11:25 ` Jan Beulich
2020-04-08 15:10 ` Roger Pau Monné
2020-04-09 11:16 ` Jan Beulich
2020-04-14 8:01 ` Roger Pau Monné
2020-04-14 9:09 ` Jan Beulich
2020-04-14 9:34 ` Roger Pau Monné
2020-04-14 9:52 ` Jan Beulich
2020-04-09 11:54 ` Jan Beulich
2020-04-10 15:48 ` Wei Liu
2020-04-14 6:28 ` Jan Beulich
2020-04-14 7:52 ` Roger Pau Monné [this message]
2020-04-14 9:01 ` Jan Beulich
2020-04-14 10:02 ` Roger Pau Monné
2020-04-14 10:13 ` Jan Beulich
2020-04-14 11:19 ` Roger Pau Monné
2020-04-14 13:50 ` Jan Beulich
2020-04-14 14:53 ` Roger Pau Monné
2020-04-14 15:06 ` Jan Beulich
2020-04-15 11:49 ` Roger Pau Monné
2020-04-15 11:51 ` Jan Beulich
2020-04-15 14:49 ` Roger Pau Monné
2020-04-15 15:42 ` Jan Beulich
2020-04-15 15:54 ` Roger Pau Monné
2020-04-15 15:59 ` Jan Beulich
2020-04-06 10:57 ` [PATCH v9 2/3] x86/tlb: allow disabling the TLB clock Roger Pau Monne
2020-04-06 10:57 ` [PATCH v9 3/3] x86/tlb: use Xen L0 assisted TLB flush when available Roger Pau Monne
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=20200414075245.GC28601@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=tim@xen.org \
--cc=wl@xen.org \
--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 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.