From: Thomas Gleixner <tglx@linutronix.de>
To: Peter Xu <peterx@redhat.com>
Cc: Ming Lei <ming.lei@redhat.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [PATCH V4] sched/isolation: isolate from handling managed interrupt
Date: Tue, 04 Feb 2020 09:13:55 +0000 [thread overview]
Message-ID: <875zgmzpd8.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20200203235743.GH155875@xz-x1>
Peter,
Peter Xu <peterx@redhat.com> writes:
> On Mon, Feb 03, 2020 at 11:15:50PM +0000, Thomas Gleixner wrote:
>> No, really. The basic guarantee is that your new kernel is going to work
>> fine with the previous command line, but making a guarantee that new
>> command line options still work on an old kernel are just creating a
>> horrible mess. So if that command line interface was not designed to
>> handle unknown arguments in the first place, you better fix that.
>
> Hi, Thomas,
>
> Just to make sure I understand it right: are you suggesting that we
> fix up housekeeping_isolcpus_setup() to be able to skip unknown sub
> parameters?
Exactly.
next prev parent reply other threads:[~2020-02-04 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 9:16 [PATCH V4] sched/isolation: isolate from handling managed interrupt Ming Lei
2020-01-22 13:25 ` Thomas Gleixner
2020-02-03 19:21 ` Peter Xu
2020-02-03 23:15 ` Thomas Gleixner
2020-02-03 23:57 ` Peter Xu
2020-02-04 9:13 ` Thomas Gleixner [this message]
2020-01-22 15:34 ` [tip: irq/core] genirq, sched/isolation: Isolate from handling managed interrupts tip-bot2 for Ming Lei
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=875zgmzpd8.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=juri.lelli@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=mingo@redhat.com \
--cc=peterx@redhat.com \
--cc=peterz@infradead.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.