From: Joerg Roedel <jroedel@suse.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Joerg Roedel <joro@8bytes.org>,
iommu@lists.linux-foundation.org, zhen-hual@hp.com,
bhe@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] iommu/vt-d: Don't consider copied context entries as present
Date: Thu, 11 Jun 2015 16:12:56 +0200 [thread overview]
Message-ID: <20150611141256.GF16345@suse.de> (raw)
In-Reply-To: <1434031622.3907.40.camel@infradead.org>
On Thu, Jun 11, 2015 at 03:07:02PM +0100, David Woodhouse wrote:
> On Thu, 2015-06-11 at 15:47 +0200, Joerg Roedel wrote:
> > From: Joerg Roedel <jroedel@suse.de>
> >
> > Hide the copied context entries from the IOMMU driver by
> > considering them as non-present. This is implemented by
> > setting the first AVL bit (bit 67) in the context entry to
> > one. If this bit is set, the context_present() function
> > returns false.
> >
> > Signed-off-by: Joerg Roedel <jroedel@suse.de>
>
> In the extended context entry, bit 67 is the PGE bit. There are no bits
> which are available to software, to my knowledge.
Ah you are right, I was looking at the context-entry format without
PASID. Then I have to solve this differently. Thanks for pointing that
out.
Joerg
next prev parent reply other threads:[~2015-06-11 14:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 13:47 [PATCH 0/4] More cleanups and fixes for Intel VT-d Joerg Roedel
2015-06-11 13:47 ` [PATCH 1/4] iommu/vt-d: Remove iommu_attach_domain_with_id() Joerg Roedel
2015-06-11 13:47 ` [PATCH 2/4] iommu/vt-d: Don't consider copied context entries as present Joerg Roedel
2015-06-11 14:07 ` David Woodhouse
2015-06-11 14:12 ` Joerg Roedel [this message]
2015-06-11 14:19 ` David Woodhouse
2015-06-11 14:25 ` Joerg Roedel
2015-06-11 14:44 ` David Woodhouse
2015-06-11 15:12 ` David Woodhouse
2015-06-11 14:51 ` Joerg Roedel
2015-06-11 13:47 ` [PATCH 3/4] iommu/vt-d: Remove unmap_device_dma() Joerg Roedel
2015-06-11 13:47 ` [PATCH 4/4] iommu/vt-d: Make sure si_domain is allocated for kdump kernel Joerg Roedel
2015-06-11 15:54 ` [PATCH 0/4] More cleanups and fixes for Intel VT-d David Woodhouse
2015-06-12 7:31 ` Joerg Roedel
2015-06-12 20:29 ` Joerg Roedel
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=20150611141256.GF16345@suse.de \
--to=jroedel@suse.de \
--cc=bhe@redhat.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhen-hual@hp.com \
/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