From: Christoph Hellwig <hch@lst.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Thomas.Lendacky@amd.com, Ashish Kalra <ashish.kalra@amd.com>,
brijesh.singh@amd.com, ssg.sos.patches@amd.com,
dave.hansen@linux-intel.com, peterz@infradead.org,
x86@kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, mingo@redhat.com, bp@alien8.de,
luto@kernel.org, hpa@zytor.com, tglx@linutronix.de, hch@lst.de
Subject: Re: [PATCH v3] swiotlb: Adjust SWIOTBL bounce buffer size for SEV guests.
Date: Fri, 6 Nov 2020 19:24:24 +0100 [thread overview]
Message-ID: <20201106182424.GA9330@lst.de> (raw)
In-Reply-To: <20201105190649.GB5366@char.us.oracle.com>
On Thu, Nov 05, 2020 at 02:06:49PM -0500, Konrad Rzeszutek Wilk wrote:
> .
> > > Right, so I am wondering if we can do this better.
> > >
> > > That is you are never going to get any 32-bit devices with SEV right? That
> > > is there is nothing that bounds you to always use the memory below 4GB?
> > >
> >
> > We do support 32-bit PCIe passthrough devices with SEV.
>
> Ewww.. Which devices would this be?
There is still some new broken shit like that that keeps appearing.
GPU is pretty famouts for supporting less than 64-bit addressing,
even if it isn't all the way down to 32-bit.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-11-06 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 22:08 [PATCH v3] swiotlb: Adjust SWIOTBL bounce buffer size for SEV guests Ashish Kalra
2020-11-04 22:14 ` Konrad Rzeszutek Wilk
2020-11-04 22:39 ` Ashish Kalra
2020-11-05 17:43 ` Konrad Rzeszutek Wilk
2020-11-05 18:41 ` Ashish Kalra
2020-11-05 19:06 ` Konrad Rzeszutek Wilk
2020-11-05 19:38 ` Ashish Kalra
2020-11-05 20:20 ` Konrad Rzeszutek Wilk
2020-11-05 21:20 ` Ashish Kalra
2020-11-13 21:19 ` Konrad Rzeszutek Wilk
2020-11-13 22:10 ` Ashish Kalra
2020-11-17 15:33 ` Ashish Kalra
2020-11-17 17:00 ` Konrad Rzeszutek Wilk
2020-11-17 17:38 ` Ashish Kalra
2020-11-17 19:04 ` Kalra, Ashish
2020-11-17 20:31 ` Konrad Rzeszutek Wilk
2020-11-06 18:24 ` Christoph Hellwig [this message]
2020-11-04 22:16 ` Andy Shevchenko
2020-11-23 15:31 ` Guilherme Piccoli
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=20201106182424.GA9330@lst.de \
--to=hch@lst.de \
--cc=Thomas.Lendacky@amd.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@linux-intel.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ssg.sos.patches@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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