From: Thomas Gleixner <tglx@linutronix.de>
To: Noam Camus <noamca@mellanox.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Chris Metcalf <cmetcalf@mellanox.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"anna-maria@linutronix.de" <anna-maria@linutronix.de>,
Eitan Rabin <rabin@mellanox.com>,
"Fu, Zhonghui" <zhonghui.fu@intel.com>
Subject: RE: Reduce Linux boot time on Large scale system
Date: Wed, 19 Apr 2017 12:35:09 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1704191229270.1829@nanos> (raw)
In-Reply-To: <DB5PR05MB1638D630B58C2F0A3522696CAA180@DB5PR05MB1638.eurprd05.prod.outlook.com>
On Wed, 19 Apr 2017, Noam Camus wrote:
Please fix your mail client to do proper line wraps around 78 chars and
proper citation. Also please trim your replies. There is no point in
scrolling through 2 pages of cited mail just to get to your question.
> > From: Thomas Gleixner [mailto:tglx@linutronix.de]
> > There might also be interaction required with the state machine,
> > i.e. stop the state progress on a self plugging CPU between two steps to
> > make serialization work.
>
> What would be a good base to start on all above? Would some formal
> release like v4.8 TAG good enough , or do I need to base on some other
> specific HEAD (or TAG)?
Errm, no. Development happens on Linus current tree or the particular
development tree/branch of a particular subsystem. In this case
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug
which is empty right now, but about to be filled up again. Start against
Linus HEAD for now.
Thanks,
tglx
prev parent reply other threads:[~2017-04-19 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM4PR05MB1636E0752C76AA42A777F81AAA0B0@AM4PR05MB1636.eurprd05.prod.outlook.com>
2017-04-19 7:49 ` Peter Zijlstra
2017-04-19 8:58 ` Thomas Gleixner
2017-04-19 10:08 ` Noam Camus
2017-04-19 10:35 ` Thomas Gleixner [this message]
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=alpine.DEB.2.20.1704191229270.1829@nanos \
--to=tglx@linutronix.de \
--cc=Vineet.Gupta1@synopsys.com \
--cc=anna-maria@linutronix.de \
--cc=cmetcalf@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=noamca@mellanox.com \
--cc=peterz@infradead.org \
--cc=rabin@mellanox.com \
--cc=zhonghui.fu@intel.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®