mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xi Ruoyao <xry111@xry111.site>
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: A question about prefetchw detection in "x86/asm: Cleanup prefetch primitives"
Date: Wed, 21 Jun 2023 21:19:34 +0800	[thread overview]
Message-ID: <29beee7faf370ea892cb4e5a85ddd1f7ee132164.camel@xry111.site> (raw)
In-Reply-To: <20230621130955.GHZJL2o771lIEPURUl@fat_crate.local>

On Wed, 2023-06-21 at 15:09 +0200, Borislav Petkov wrote:
> On Wed, Jun 21, 2023 at 09:06:51PM +0800, Xi Ruoyao wrote:
> > I think it's not an issue in the kernel itself, but announcing
> > 3dnowprefetch in /proc/cpuinfo for an old Intel CPU w/o real prefetchw
> > implementation seems problematic (to me).
> 
> And this is a problem because?

If a code generator parses /proc/cpuinfo for CPU capabilities, it may
generates a no-op prefetchw instead of prefetcht0 as a fallback.

> 
> Think practically.
> 

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University

  reply	other threads:[~2023-06-21 13:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-21 10:57 Xi Ruoyao
2023-06-21 11:13 ` Borislav Petkov
2023-06-21 11:18   ` Xi Ruoyao
2023-06-21 12:04     ` Xi Ruoyao
2023-06-21 12:57       ` Borislav Petkov
2023-06-21 13:06         ` Xi Ruoyao
2023-06-21 13:09           ` Borislav Petkov
2023-06-21 13:19             ` Xi Ruoyao [this message]
2023-06-21 13:46               ` Borislav Petkov
2023-06-21 13:47                 ` Xi Ruoyao
2023-06-21 13:57                   ` Borislav Petkov

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=29beee7faf370ea892cb4e5a85ddd1f7ee132164.camel@xry111.site \
    --to=xry111@xry111.site \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®