All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com, ehabkost@redhat.com,
	rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] intel_iommu: large page support
Date: Fri, 15 Jan 2016 11:15:40 +0800	[thread overview]
Message-ID: <5698645C.2070504@redhat.com> (raw)
In-Reply-To: <20160114112703-mutt-send-email-mst@redhat.com>



On 01/14/2016 05:28 PM, Michael S. Tsirkin wrote:
> On Thu, Jan 14, 2016 at 12:47:24AM -0500, Jason Wang wrote:
>> > Current intel_iommu only supports 4K page which may not be sufficient
>> > to cover guest working set. This patch tries to enable 2M and 1G mapping
>> > for intel_iommu. This is also useful for future device IOTLB
>> > implementation to have a better hit rate.
>> > 
>> > Major work is adding a page mask field on IOTLB entry to make it
>> > support large page. And also use the slpte level as key to do IOTLB
>> > lookup. MAMV was increased to 18 to support direct invalidation for 1G
>> > mapping.
>> > 
>> > Cc: Michael S. Tsirkin <mst@redhat.com>
>> > Cc: Paolo Bonzini <pbonzini@redhat.com>
>> > Cc: Richard Henderson <rth@twiddle.net>
>> > Cc: Eduardo Habkost <ehabkost@redhat.com>
>> > Signed-off-by: Jason Wang <jasowang@redhat.com>
> Looks good, thanks!
>
> I was going to comment that changes such as MAMV would
> have to be versioned, when I noticed that this device
> is unmigrateable ATM.
>
> So no issue, but we do need to fix migration for it.
>

Yes, it was in my TODO list. Will first see if there're more caps that
needs to be added. (Otherwise, we may have a long property list for iommu).

      reply	other threads:[~2016-01-15  3:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14  5:47 [Qemu-devel] [PATCH] intel_iommu: large page support Jason Wang
2016-01-14  9:28 ` Michael S. Tsirkin
2016-01-15  3:15   ` Jason Wang [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=5698645C.2070504@redhat.com \
    --to=jasowang@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.