From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Joerg Roedel <jroedel@suse.de>, Andi Kleen <ak@linux.intel.com>,
Borislav Petkov <bp@alien8.de>, Andy Lutomirski <luto@kernel.org>,
Sean Christopherson <seanjc@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
David Rientjes <rientjes@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
Tom Lendacky <thomas.lendacky@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Varad Gautam <varad.gautam@suse.com>,
Dario Faggioli <dfaggioli@suse.com>,
x86@kernel.org, linux-mm@kvack.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH 1/5] mm: Add support for unaccepted memory
Date: Fri, 13 Aug 2021 00:23:14 +0300 [thread overview]
Message-ID: <20210812212314.4fkrmzebluyl3umo@box.shutemov.name> (raw)
In-Reply-To: <708c758f-2305-4fe6-ddcd-6881794402a5@intel.com>
On Thu, Aug 12, 2021 at 01:59:01PM -0700, Dave Hansen wrote:
> On 8/12/21 1:49 PM, Kirill A. Shutemov wrote:
> > On Thu, Aug 12, 2021 at 07:14:20AM -0700, Dave Hansen wrote:
> >> On 8/12/21 1:19 AM, Joerg Roedel wrote:
> >> maybe_accept_page()
> >> {
> >> unsigned long huge_pfn = page_to_phys(page) / PMD_SIZE;
> >>
> >> /* Test the bit before taking any locks: */
> >> if (test_bit(huge_pfn, &accepted_bitmap))
> >> return;
> >>
> >> spin_lock_irq();
> >> /* Retest inside the lock: */
> >> if (test_bit(huge_pfn, &accepted_bitmap))
> >> return;
> >> tdx_accept_page(page, PMD_SIZE);
> >> set_bit(huge_pfn, &accepted_bitmap));
> >> spin_unlock_irq();
> >> }
> >>
> >> That's still not great. It's still a global lock and the lock is still
> >> held for quite a while because that accept isn't going to be lightning
> >> fast. But, at least it's not holding any *other* locks. It also
> >> doesn't take any locks in the fast path where the 2MB page was already
> >> accepted.
> >
> > I expect a cache line with bitmap to bounce around during warm up. One
> > cache line covers a gig of RAM.
>
> The bitmap bouncing around isn't going to really matter when you have a
> global lock protecting it from writes.
The idea with static key would not work if we mark shared memory as
unaccepted there.
> > It's also not clear at all at what point the static key has to be
> > switched. We don't have any obvious point where we can say we are done
> > with accepting (unless you advocate for proactive accepting).
>
> Two easy options:
> 1. Run over the bitmap and counts the bits left. That can be done
> outside the lock even.
> 2. Keep a counter of the number of bits set in the bitmap.
>
> > I like PageOffline() because we only need to consult the cache page
> > allocator already have in hands before looking into bitmap.
>
> I like it too. But, it's really nasty if the value is only valid deep
> in the allocator.
>
> We could keep the PageOffline() thing and then move it to some other
> field in 'struct page' that's only valid between ClearPageOffline() and
> prep_new_page(). Some magic value that says: "This page has not yet
> been accepted, you better check the bitmap." Something like:
>
> if (TestClearPageOffline(page))
> page->private = 0Xdeadbeef;
>
> and then check page->private in prep_new_page(). There should be plenty
> of 'struct page' space to hijack in that small window.
PageOffline() encoded in mapcount and check_new_page_bad() would complain
is mapcount is not -1.
> BTW, I was going to actually try and hack something up, but I got
> annoyed that your patches don't apply upstream and gave up. A git tree
> with all of the dependencies would be nice. <hint, hint>
Okay.
--
Kirill A. Shutemov
next prev parent reply other threads:[~2021-08-12 21:23 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 6:26 [PATCH 0/5] x86: Impplement support for unaccepted memory Kirill A. Shutemov
2021-08-10 6:26 ` [PATCH 1/5] mm: Add " Kirill A. Shutemov
2021-08-10 7:48 ` David Hildenbrand
2021-08-10 15:02 ` Kirill A. Shutemov
2021-08-10 15:21 ` David Hildenbrand
2021-08-12 20:34 ` Kirill A. Shutemov
2021-08-10 18:13 ` Dave Hansen
2021-08-10 18:30 ` Andi Kleen
2021-08-10 18:56 ` Dave Hansen
2021-08-10 19:23 ` Andi Kleen
2021-08-10 19:46 ` Dave Hansen
2021-08-10 21:20 ` Andi Kleen
2021-08-12 8:19 ` Joerg Roedel
2021-08-12 14:14 ` Dave Hansen
2021-08-12 20:49 ` Kirill A. Shutemov
2021-08-12 20:59 ` Dave Hansen
2021-08-12 21:23 ` Kirill A. Shutemov [this message]
2021-08-13 14:49 ` Joerg Roedel
2021-08-17 15:00 ` David Hildenbrand
2021-08-19 9:55 ` Joerg Roedel
2021-08-19 10:06 ` David Hildenbrand
2021-08-10 20:50 ` Dave Hansen
2021-08-12 21:08 ` Kirill A. Shutemov
2021-08-10 6:26 ` [PATCH 2/5] efi/x86: Implement " Kirill A. Shutemov
2021-08-10 17:50 ` Dave Hansen
2021-08-12 21:14 ` Kirill A. Shutemov
2021-08-12 21:43 ` Dave Hansen
2021-08-10 18:30 ` Dave Hansen
2021-08-10 19:08 ` Kirill A. Shutemov
2021-08-10 19:19 ` Dave Hansen
2021-08-12 21:17 ` Kirill A. Shutemov
2021-08-10 6:26 ` [PATCH 3/5] x86/boot/compressed: Handle " Kirill A. Shutemov
2021-08-10 6:26 ` [PATCH 4/5] x86/mm: Provide helpers for " Kirill A. Shutemov
2021-08-10 18:16 ` Dave Hansen
2021-08-12 20:31 ` Kirill A. Shutemov
2021-08-10 6:26 ` [PATCH 5/5] x86/tdx: Unaccepted memory support Kirill A. Shutemov
2021-08-10 14:08 ` [PATCH 0/5] x86: Impplement support for unaccepted memory Dave Hansen
2021-08-10 15:15 ` Kirill A. Shutemov
2021-08-10 15:51 ` Dave Hansen
2021-08-10 17:31 ` Kirill A. Shutemov
2021-08-10 17:36 ` Dave Hansen
2021-08-10 17:51 ` Kirill A. Shutemov
2021-08-10 18:19 ` Dave Hansen
2021-08-10 18:39 ` Kirill A. Shutemov
2021-08-12 8:23 ` Joerg Roedel
2021-08-12 10:10 ` Kirill A. Shutemov
2021-08-12 19:33 ` Andi Kleen
2021-08-12 20:22 ` Kirill A. Shutemov
2021-08-13 14:56 ` 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=20210812212314.4fkrmzebluyl3umo@box.shutemov.name \
--to=kirill@shutemov.name \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dfaggioli@suse.com \
--cc=jroedel@suse.de \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=varad.gautam@suse.com \
--cc=vbabka@suse.cz \
--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).