mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Fang <peter.fang@intel.com>
To: "Li, Xiaoyao" <Xiaoyao.Li@intel.com>
Cc: Kuppuswamy Sathyanarayanan
	<sathyanarayanan.kuppuswamy@linux.intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Kiryl Shutsemau <kas@kernel.org>,
	"Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>, "x86@kernel.org" <x86@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Binbin Wu <binbin.wu@linux.intel.com>
Subject: Re: [PATCH v3 3/4] virt: tdx-guest: Use a variable to store the Quote buffer size
Date: Wed, 16 Sep 2026 02:44:33 -0700	[thread overview]
Message-ID: <aqplAYSXnO60T-a_@intel.com> (raw)
In-Reply-To: <apoerDLC_fpSupY5@intel.com>

On Thu, Sep 03, 2026 at 06:28:12PM -0700, Peter Fang wrote:
> On Thu, Sep 03, 2026 at 01:59:25PM +0800, Xiaoyao Li wrote:
> > On 9/3/2026 7:15 AM, Peter Fang wrote:
> > > You are also dropping PAGE_ALIGN() in alloc and free calls. You can
> > > mention it in commit log.
> > 
> > I think it's better to keep the PAGE_ALIGN() when assign quote_data_len,
> > although GET_QUOTE_BUF_SIZE is aligned already. This makes it super clear
> > we want to page size align the buffer.
> > 
> > And in next patch, we can make it
> > 
> >   quote_data_len = PAGE_ALIGN(get_quote_buf_size());
> 
> Hmm... Looking at this again actually makes me think it could be
> reworked a bit. There's a discrepancy in alloc_quote_buf() if for
> whatever reason @len is not page aligned. alloc_pages_exact() rounds it
> up internally but set_memory_decrypted() rounds it *down*, so we'd end
> up with a useless page at the end...
> 
> What if alloc_quote_buf() took a @npages instead? Then the expectations
> would be pretty clear:

I took your suggestion in v4 [1]. The @npages approach was more work
than expected and made the series bigger. This is simpler.

[1] https://lore.kernel.org/all/20260915092632.2822169-5-peter.fang@intel.com/

> 
> 

  reply	other threads:[~2026-09-16  9:44 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29 12:29 [PATCH v3 0/4] tdx-guest: Make Quote buffer size dynamic Peter Fang
2026-07-29 12:29 ` [PATCH v3 1/4] x86/tdx: Add helper to query maximum TD Quote size Peter Fang
2026-09-03  6:04   ` Tony Lindgren
2026-09-03 22:45     ` Peter Fang
2026-07-29 12:29 ` [PATCH v3 2/4] virt: tdx-guest: Calculate the Quote buffer size safely Peter Fang
2026-07-29 18:29   ` Kuppuswamy Sathyanarayanan
2026-09-03  5:33   ` Xiaoyao Li
2026-09-03  6:05   ` Tony Lindgren
2026-09-03  9:18   ` Binbin Wu
2026-07-29 12:29 ` [PATCH v3 3/4] virt: tdx-guest: Use a variable to store the Quote buffer size Peter Fang
2026-07-29 18:47   ` Kuppuswamy Sathyanarayanan
2026-09-02 23:15     ` Peter Fang
2026-09-03  5:59       ` Xiaoyao Li
2026-09-04  1:28         ` Peter Fang
2026-09-16  9:44           ` Peter Fang [this message]
2026-09-16  9:32       ` Peter Fang
2026-09-03  6:31   ` Tony Lindgren
2026-09-04  4:51     ` Peter Fang
2026-09-03  9:17   ` Binbin Wu
2026-09-04  6:49     ` Peter Fang
2026-09-07  7:55       ` Binbin Wu
2026-09-10 21:39         ` Peter Fang
2026-07-29 12:29 ` [PATCH v3 4/4] virt: tdx-guest: Allocate Quote buffer dynamically Peter Fang
2026-09-03  6:21   ` Xiaoyao Li
2026-09-03  6:33     ` Tony Lindgren
2026-09-04 20:59       ` Peter Fang
2026-09-08  4:23         ` Tony Lindgren
2026-07-29 21:21 ` [PATCH v3 0/4] tdx-guest: Make Quote buffer size dynamic Edgecombe, Rick P
2026-08-11 22:40   ` Edgecombe, Rick P
2026-08-12 14:08     ` Sean Christopherson
2026-08-12 16:02       ` Edgecombe, Rick P
2026-08-12 16:43         ` Sean Christopherson
2026-08-12 17:22           ` Edgecombe, Rick P
2026-08-12 22:37             ` Peter Fang
2026-08-12 22:47               ` Edgecombe, Rick P
2026-08-12 23:10                 ` Sean Christopherson
2026-08-12 23:30                   ` Edgecombe, Rick P
2026-08-13 19:32                     ` Artem Bityutskiy
2026-08-13 20:14                       ` Edgecombe, Rick P
2026-08-14  5:45                         ` Artem Bityutskiy
2026-08-14  7:37                           ` Peter Fang
2026-08-14 15:55                           ` Edgecombe, Rick P
2026-08-15 11:39                             ` Artem Bityutskiy
2026-08-17 17:26                               ` Edgecombe, Rick P
2026-08-18 11:09                                 ` Artem Bityutskiy
2026-08-18 20:37                       ` Sean Christopherson
2026-08-18 23:46                         ` Edgecombe, Rick P
2026-08-19 14:57                         ` Artem Bityutskiy
2026-08-12 23:27                 ` Peter Fang
2026-08-12 21:02         ` Peter Fang
2026-08-27 22:22   ` Peter Fang
2026-08-27 22:41     ` Edgecombe, Rick P

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=aqplAYSXnO60T-a_@intel.com \
    --to=peter.fang@intel.com \
    --cc=Xiaoyao.Li@intel.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kas@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=tglx@kernel.org \
    --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

all inboxes | Powered by JetHome®