From: "H. Peter Anvin" <hpa@zytor.com>
To: Nikolay Borisov <nik.borisov@suse.com>,
"Xin Li (Intel)" <xin@zytor.com>,
linux-kernel@vger.kernel.org
Cc: luto@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org
Subject: Re: [PATCH v3 1/1] x86/fred: Fix INT80 emulation for FRED
Date: Wed, 17 Apr 2024 08:07:16 -0700 [thread overview]
Message-ID: <2d0e67dd-c3e3-4701-839a-68d73c61c170@zytor.com> (raw)
In-Reply-To: <d0979bd9-fd12-4672-b451-23f23fc2353c@suse.com>
On 4/17/24 04:02, Nikolay Borisov wrote:
>
> On 17.04.24 г. 9:30 ч., Xin Li (Intel) wrote:
>> Add a FRED-specific INT80 handler fred_int80_emulation():
>>
>> 1) As INT instructions and hardware interrupts are separate event
>> types, FRED does not preclude the use of vector 0x80 for external
>> interrupts. As a result the FRED setup code does *NOT* reserve
>> vector 0x80 and calling int80_is_external() is not merely
>> suboptimal but actively incorrect: it could cause a system call
>> to be incorrectly ignored.
>>
>> 2) fred_int80_emulation(), only called for handling vector 0x80 of
>> event type EVENT_TYPE_SWINT, will NEVER be called to handle any
>> external interrupt (event type EVENT_TYPE_EXTINT).
>>
>> 3) The FRED kernel entry handler does *NOT* dispatch INT instructions,
>> which is of event type EVENT_TYPE_SWINT, so compared with
>> do_int80_emulation(), there is no need to do any user mode check.
>>
>> 4) int80_emulation() does a CLEAR_BRANCH_HISTORY, which is likely
>> > overkill for new x86 CPU implementations that support FRED.
>
> Well, that's a bit of an overstatement/speculation, because
> clear_branch_history will only be effective if the machine is
> susceptible to the given bug and there isn't a better options (i.e using
> a hardware bit controlling the respective aspect of the CPU).
>>
It would seem like a huge stretch to expect that a FRED-capable CPU
would not have such a facility. This is a matter of establishing a
baseline for FRED-capable hardware.
It would make more sense to me to add it if we turn out to need it; note
that FRED code is currently only enabled on demand, in order to defend
against bit rot until we have physical hardware.
Now, if this is still desired, it *probably* belongs better in either
fred_intx()/fred_other() or asm_fred_entrypoint_user, depending on if
this ought to be done for all entries from userspace or only system calls.
-hpa
next prev parent reply other threads:[~2024-04-17 15:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 6:30 Xin Li (Intel)
2024-04-17 9:38 ` Borislav Petkov
2024-04-17 14:59 ` H. Peter Anvin
2024-04-17 15:34 ` Xin Li
2024-04-17 20:28 ` Borislav Petkov
2024-04-17 15:06 ` Xin Li
2024-04-17 15:09 ` H. Peter Anvin
2024-04-17 11:02 ` Nikolay Borisov
2024-04-17 15:07 ` H. Peter Anvin [this message]
2024-04-17 15:55 ` Xin Li
2024-04-17 16:39 ` H. Peter Anvin
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=2d0e67dd-c3e3-4701-839a-68d73c61c170@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
/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®