From: Paul Durrant <Paul.Durrant@citrix.com>
To: Brian Woods <brian.woods@amd.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v3] amd-iommu: remove page merging code
Date: Mon, 3 Dec 2018 10:27:25 +0000 [thread overview]
Message-ID: <3d18c49a5b7149b5b6ef09c342cd2fd5@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <827a9ca9-80b5-1ab9-3fb0-24e6a94b3918@citrix.com>
Ping? Can I get an ack or otherwise from an AMD maintainer please?
Paul
> -----Original Message-----
> From: Andrew Cooper
> Sent: 28 November 2018 10:41
> To: Paul Durrant <Paul.Durrant@citrix.com>; xen-devel@lists.xenproject.org
> Cc: Brian Woods <brian.woods@amd.com>; Suravee Suthikulpanit
> <suravee.suthikulpanit@amd.com>
> Subject: Re: [Xen-devel] [PATCH v3] amd-iommu: remove page merging code
>
> On 28/11/2018 09:55, Paul Durrant wrote:
> > The page merging logic makes use of bits 1-8 and bit 63 of a PTE, which
> > used to be specified as 'ignored'. However, bits 5 and 6 are now
> specified
> > as 'accessed' and 'dirty' bits and their use only remains safe as long
> as
> > the DTE 'Host Access Dirty' bits remain unused by Xen, or by hardware
> > before the domain starts running. (XSA-275 disabled the operation of the
> > code after domain creation completes).
> >
> > With the page merging logic present in its current form there are no
> spare
> > ignored bits in the PTE at all, but PV-IOMMU support will require at
> least
> > one spare bit to track which PTEs are added by hypercall.
> >
> > This patch removes the code, freeing up the remaining PTE ignored bits
> > for other use, including PV-IOMMU support, as well as significantly
> > simplifying and shortening the source by ~170 lines. There may be some
> > marginal performance cost (but none has been observed in manual testing
> > with a passed-through NVIDIA GPU) since higher order mappings will now
> be
> > ruled out until a mapping order parameter is passed to iommu_ops. That
> will
> > be dealt with by a subsequent patch though.
> >
> > Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
>
> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-03 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 9:55 [PATCH v3] amd-iommu: remove page merging code Paul Durrant
2018-11-28 10:41 ` Andrew Cooper
2018-12-03 10:27 ` Paul Durrant [this message]
2018-12-04 23:31 ` Woods, Brian
2018-12-05 8:50 ` Paul Durrant
2018-12-11 11:00 ` Paul Durrant
2018-12-11 11:22 ` Jan Beulich
2018-12-11 11:30 ` Paul Durrant
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=3d18c49a5b7149b5b6ef09c342cd2fd5@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=brian.woods@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--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 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).