From: Dave Hansen <dave.hansen@intel.com>
To: andrzej zaborowski <balrogg@gmail.com>
Cc: "Huang, Kai" <kai.huang@intel.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
x86@kernel.org, linux-sgx@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
Tony Luck <tony.luck@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86: sgx: Don't track poisoned pages for reclaiming
Date: Tue, 11 Feb 2025 16:37:25 -0800 [thread overview]
Message-ID: <294b456a-e43f-4f89-a643-8f45496ed6ed@intel.com> (raw)
In-Reply-To: <CAOq732KGpve688KWFCh1zdrme3vm7GxEiw6UjHswk5h6B3cNDg@mail.gmail.com>
On 2/11/25 16:32, andrzej zaborowski wrote:
>> Actually, now that I think about it even more, why would ETRACK or
>> EBLOCK access the page itself? They seem superficially like they'd be
>> metadata-only too.
> I haven't seen a crash in either of these (always in EWB), I didn't
> want to imply that. But starting that sequence seems wrong knowing we
> cannot reclaim the page.
That's kinda another reason not to delve into the details too deeply. I
think you wanted to talk about the "writeback process" as a thing and
not really about "ETRACK, EBLOCK and EWB" per se.
Writing back an SGX page is the problem. The names of the three
instructions that implement the writeback or that there _are_ even three
of them isn't super relevant.
next prev parent reply other threads:[~2025-02-12 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 15:01 [PATCH] x86: sgx: Don't track poisoned pages for reclaiming Andrew Zaborowski
2025-02-11 16:25 ` Dave Hansen
2025-02-11 21:03 ` Jarkko Sakkinen
2025-02-11 21:18 ` Huang, Kai
2025-02-11 23:24 ` Jarkko Sakkinen
2025-02-11 23:31 ` Dave Hansen
2025-02-12 0:32 ` andrzej zaborowski
2025-02-12 0:37 ` Dave Hansen [this message]
2025-02-12 10:38 ` Huang, Kai
2025-02-12 21:25 ` Jarkko Sakkinen
2025-02-12 0:22 ` Andrew Zaborowski
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=294b456a-e43f-4f89-a643-8f45496ed6ed@intel.com \
--to=dave.hansen@intel.com \
--cc=balrogg@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jarkko@kernel.org \
--cc=kai.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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