From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas.Lendacky@amd.com, Ashish Kalra <Ashish.Kalra@amd.com>,
jon.grimm@amd.com, brijesh.singh@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,
luto@kernel.org, hpa@zytor.com, rientjes@google.com,
tglx@linutronix.de, hch@lst.de
Subject: Re: [PATCH v6] swiotlb: Adjust SWIOTBL bounce buffer size for SEV guests.
Date: Mon, 23 Nov 2020 13:43:27 -0500 [thread overview]
Message-ID: <20201123184327.GA22269@char.us.oracle.com> (raw)
In-Reply-To: <20201123180215.GG15044@zn.tnic>
On Mon, Nov 23, 2020 at 07:02:15PM +0100, Borislav Petkov wrote:
> On Mon, Nov 23, 2020 at 12:56:32PM -0500, Konrad Rzeszutek Wilk wrote:
> > This is not going to work for TDX. I think having a registration
> > to SWIOTLB to have this function would be better going forward.
> >
> > As in there will be a swiotlb_register_adjuster() which AMD SEV
> > code can call at start, also TDX can do it (and other platforms).
>
> Oh do tell. It doesn't need to adjust size?
I am assuming that TDX is going to have the same exact issue that
AMD SEV will have.
Are you recommending to have an unified x86 specific callback
where we check if it:
- CPUID_AMD_SEV or CPUID_INTEL_TDX is set, and
- No vIOMMU present, then we adjust the size?
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-11-23 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 21:42 [PATCH v6] swiotlb: Adjust SWIOTBL bounce buffer size for SEV guests Ashish Kalra
2020-11-23 17:06 ` Borislav Petkov
2020-11-23 17:56 ` Konrad Rzeszutek Wilk
2020-11-23 18:02 ` Borislav Petkov
2020-11-23 18:43 ` Konrad Rzeszutek Wilk [this message]
2020-11-24 9:00 ` Borislav Petkov
2020-11-23 22:56 ` Ashish Kalra
2020-11-24 9:04 ` Borislav Petkov
2020-11-24 9:25 ` Kalra, Ashish
2020-11-24 9:38 ` Borislav Petkov
2020-11-24 9:43 ` Kalra, Ashish
2020-11-24 23:46 ` Ashish Kalra
2020-12-01 20:42 ` Konrad Rzeszutek Wilk
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=20201123184327.GA22269@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=Ashish.Kalra@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@alien8.de \
--cc=brijesh.singh@amd.com \
--cc=dave.hansen@linux-intel.com \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jon.grimm@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).