From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Zijlstra <peterz@infradead.org>, Ondrej Zary <linux@zary.sk>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] x86/iopl: Fake iopl(3) CLI/STI usage
Date: Fri, 17 Sep 2021 14:33:18 +0200 [thread overview]
Message-ID: <87mtob8jqp.ffs@tglx> (raw)
In-Reply-To: <YUSCDX5QwzTcCPFa@hirez.programming.kicks-ass.net>
On Fri, Sep 17 2021 at 13:54, Peter Zijlstra wrote:
>> [ 14.876824] fixup_iopl_exception: 333 callbacks suppressed
>> [ 14.876832] traps: hpasmd[360] attempts to use CLI/STI, pretending it's a NOP, ip:80a5356
>
> I'd say...
>
> Not sure it's really worth it, but something like the below might
> help.
One entry per task is really good enough. Though that wont help for such
stuff which is started over and over again....
Thanks,
tglx
next prev parent reply other threads:[~2021-09-17 12:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 12:23 IOPL emulation breaks hpasmd (hp-health) needed by HP DL380 G4 servers Ondrej Zary
2021-09-16 17:09 ` Thomas Gleixner
2021-09-16 20:27 ` Ondrej Zary
2021-09-16 21:05 ` Peter Zijlstra
2021-09-17 8:11 ` Ondrej Zary
2021-09-17 9:20 ` [PATCH] x86/iopl: Fake iopl(3) CLI/STI usage Peter Zijlstra
2021-09-17 10:29 ` Ondrej Zary
2021-09-17 11:54 ` Peter Zijlstra
2021-09-17 12:33 ` Thomas Gleixner [this message]
2021-09-17 12:54 ` Ondrej Zary
2021-09-17 10:40 ` Thomas Gleixner
2021-09-17 22:23 ` Linus Torvalds
2021-09-17 22:24 ` Linus Torvalds
2021-09-18 7:05 ` Peter Zijlstra
2021-09-18 9:06 ` Peter Zijlstra
2021-09-18 15:53 ` Ondrej Zary
2021-09-18 16:35 ` Linus Torvalds
2021-09-21 7:28 ` [tip: x86/core] " tip-bot2 for Peter Zijlstra
2021-09-21 11:09 ` Ondrej Zary
2021-09-21 12:00 ` Peter Zijlstra
2021-09-21 17:31 ` Ondrej Zary
2021-09-21 12:41 ` tip-bot2 for Peter Zijlstra
2021-09-21 21:01 ` [PATCH] " Andy Lutomirski
2021-09-16 21:25 ` IOPL emulation breaks hpasmd (hp-health) needed by HP DL380 G4 servers Thomas Gleixner
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=87mtob8jqp.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@zary.sk \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.