linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jianxiong Gao <jxgao@google.com>
To: vbabka@suse.cz
Cc: aarcange@redhat.com, ak@linux.intel.com,
	akpm@linux-foundation.org,  ardb@kernel.org, bp@alien8.de,
	dave.hansen@intel.com, david@redhat.com,  dfaggioli@suse.com,
	jroedel@suse.de, kirill.shutemov@linux.intel.com,
	 linux-coco@lists.linux.dev, linux-efi@vger.kernel.org,
	 linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	luto@kernel.org,
	 Marcelo Henrique Cerri <marcelo.cerri@canonical.com>,
	mgorman@techsingularity.net, mingo@redhat.com,
	 nik.borisov@suse.com, pbonzini@redhat.com, peterx@redhat.com,
	 peterz@infradead.org, philip.cox@canonical.com,
	 David Rientjes <rientjes@google.com>,
	rppt@kernel.org,  sathyanarayanan.kuppuswamy@linux.intel.com,
	 Sean Christopherson <seanjc@google.com>,
	stable@kernel.org, tglx@linutronix.de,  thomas.lendacky@amd.com,
	tim.gardner@canonical.com, x86@kernel.org
Subject: Re: [PATCHv2] efi/unaccepted: Fix soft lockups caused by parallel memory acceptance
Date: Wed, 18 Oct 2023 11:54:44 -0700	[thread overview]
Message-ID: <CAMGD6P2+JT5o3jA6d=_72rMoGB3t+uGZSrhE-TJux-VU9Xq8=Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 217 bytes --]

Tested-by: Jianxiong Gao <jxgao@google.com>

The patch helps us gain more stability in our testing.
We are not able to reproduce the soft lockup issue in over 20 runs with 176
vcpus so far.

Thanks!
-- 
Jianxiong Gao

[-- Attachment #2: Type: text/html, Size: 487 bytes --]

             reply	other threads:[~2023-10-18 18:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 18:54 Jianxiong Gao [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-18 18:56 Jianxiong Gao
2023-10-16 16:31 Kirill A. Shutemov
2023-10-16 16:41 ` Vlastimil Babka
2023-10-16 17:55 ` Matthew Wilcox
2023-10-16 21:39   ` Kirill A. Shutemov
2023-10-17  7:42     ` Ard Biesheuvel
2023-10-17  9:44       ` Kirill A. Shutemov
2023-10-17  9:57         ` Ard Biesheuvel
2023-10-17 10:17       ` Peter Zijlstra
2023-10-17 15:36         ` Ard Biesheuvel
2023-10-16 20:54 ` Michael Roth
2023-10-17  7:02   ` Vlastimil Babka
2023-11-01  0:45     ` Michael Roth
2023-11-02 13:56       ` Kirill A. Shutemov
2023-11-03  0:01         ` Michael Roth

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='CAMGD6P2+JT5o3jA6d=_72rMoGB3t+uGZSrhE-TJux-VU9Xq8=Q@mail.gmail.com' \
    --to=jxgao@google.com \
    --cc=aarcange@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=david@redhat.com \
    --cc=dfaggioli@suse.com \
    --cc=jroedel@suse.de \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=marcelo.cerri@canonical.com \
    --cc=mgorman@techsingularity.net \
    --cc=mingo@redhat.com \
    --cc=nik.borisov@suse.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=peterz@infradead.org \
    --cc=philip.cox@canonical.com \
    --cc=rientjes@google.com \
    --cc=rppt@kernel.org \
    --cc=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=seanjc@google.com \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=tim.gardner@canonical.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