mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Xin Li (Intel)" <xin@zytor.com>,
	linux-kernel@vger.kernel.org, luto@kernel.org,
	tglx@linutronix.de, mingo@redhat.com,
	dave.hansen@linux.intel.com, x86@kernel.org
Subject: Re: [PATCH v1 1/1] x86/fred: Fix int80 emulation for FRED
Date: Tue, 16 Apr 2024 11:11:44 -0700	[thread overview]
Message-ID: <e3fbd500-f6b8-49ea-addb-bbc4803709ce@zytor.com> (raw)
In-Reply-To: <20240416180746.GFZh6-cmZqCF6KX5tt@fat_crate.local>

On 4/16/24 11:07, Borislav Petkov wrote:
> On Tue, Apr 16, 2024 at 11:05:09AM -0700, H. Peter Anvin wrote:
>> The question was if you wanted a quick fix for x86/urgent. It's pretty
>> obvious that a FRED fork of the int80 code is called for.
> 
> Yeah, I'm thinking the FRED fork would be even easier to send to Linus
> now since no existing hw will break.

Looking at the resulting code (Xin's v2 path), I would agree with you. 
The code is downright trivial.

> Btw, I presume that patch needs to have
> 
> Fixes: 55617fb991df ("x86/entry: Do not allow external 0x80 interrupts")
> 

Yes. My fault, I gave Xin incorrect information w.r.t. Fixes: tags.

	-hpa


  reply	other threads:[~2024-04-16 18:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 23:40 Xin Li (Intel)
2024-04-15 16:21 ` H. Peter Anvin
2024-04-16 10:11 ` Borislav Petkov
2024-04-16 16:58   ` Xin Li
2024-04-16 18:05   ` H. Peter Anvin
2024-04-16 18:07     ` Borislav Petkov
2024-04-16 18:11       ` H. Peter Anvin [this message]
2024-04-16 18:18         ` Borislav Petkov
2024-04-16 18:19           ` 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=e3fbd500-f6b8-49ea-addb-bbc4803709ce@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=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®