LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-tip-commits@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>, x86 <x86@kernel.org>
Subject: Re: [tip: irq/core] x86: Select HARDIRQS_SW_RESEND on x86
Date: Thu, 12 Mar 2020 15:05:38 +0100	[thread overview]
Message-ID: <231875e7-fc72-edb4-a4de-fc7cfc3cdca3@redhat.com> (raw)
In-Reply-To: <CACRpkdb7vxSaK1Df6gNX_Kq-LF=S1qx2iKdmBy1Ku0vEpDVPbA@mail.gmail.com>

Hi,

On 3/12/20 3:02 PM, Linus Walleij wrote:
> On Thu, Mar 12, 2020 at 2:49 PM Hans de Goede <hdegoede@redhat.com> wrote:
> 
> [Me]
>>> I see that ARM and ARM64 simply just select this. What
>>> happens if you do that and why is x86 not selecting it in general?
>>
>> Erm, "selecting it in general" (well at least on x86) is what
>> this patch is doing.
> 
> Sorry that I was unclear, what I meant to say is why wasn't
> this done ages ago since so many important architectures seem
> to have it enabled by default.
> 
> I suppose the reason would be something like "firmware/BIOS
> should handle that for us" and recently that has started to
> break apart and x86 platforms started to be more like ARM?

That (x86 becoming more like ARM, sorta, kinda) as well as
that turning it on on x86 was not safe until Thomas wrote
the 2 patches which are marked as dependencies in the commit
message for this patch.

Regards,

Hans


  reply	other threads:[~2020-03-12 14:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 21:02 [RFC v2] x86: Select HARDIRQS_SW_RESEND on x86 Hans de Goede
2020-01-24 15:19 ` Thomas Gleixner
2020-03-11 18:24   ` Hans de Goede
2020-03-11 21:31     ` Thomas Gleixner
2020-03-11 21:49       ` Hans de Goede
2020-03-11 22:09         ` Thomas Gleixner
2020-03-12 12:06           ` Hans de Goede
2020-03-11 21:42 ` [tip: irq/core] " tip-bot2 for Hans de Goede
2020-03-12 13:31   ` Linus Walleij
2020-03-12 13:49     ` Hans de Goede
2020-03-12 14:02       ` Linus Walleij
2020-03-12 14:05         ` Hans de Goede [this message]
2020-03-12 15:55     ` 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=231875e7-fc72-edb4-a4de-fc7cfc3cdca3@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@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;
as well as URLs for NNTP newsgroup(s).