From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>
Subject: Re: [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support
Date: Thu, 7 Sep 2017 10:13:20 +0200 [thread overview]
Message-ID: <20170907081320.f5shfxcig734bmpd@gmail.com> (raw)
In-Reply-To: <20170907080709.hwospdejr2ztmqr7@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
>
> * Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> > On Tue, Sep 5, 2017 at 2:40 PM, Ingo Molnar <mingo@kernel.org> wrote:
> > >
> > > Hm, just as background, there are no regression reports I'm aware of
> > > against any of these trees, plus most of the dangerous commits have
> > > been in linux-next for at least two weeks - the majority of them even
> > > longer. The last 2-4 commits of x86/mm are fresher.
> >
> > Side note: I do not believe a lot of people actually run linux-next on
> > laptops, so suspend/resume likely doesn't get a lot of testing in
> > next.
> >
> > I think most people who run linux-next tend to be automation things on farms.
>
> Yeah, so 10af6235e0d3 was in linux-next for over a month, yet no-one reported the
> bug.
That was also smack in the middle of the vacation season on the northern
hemisphere, which didn't help testing coverage either I suspect ...
In hindsight it was perhaps not the smartest thing from me to send three major
hw-enablement features to you - although only PCID was the one that should have
real widespread effects, and I did stage those changes pretty conservatively over
several months. Hindsight is 20/20 ...
Thanks,
Ingo
next prev parent reply other threads:[~2017-09-07 8:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 9:31 [GIT PULL] x86/mm changes for v4.14: PCID support, 5-level paging support, Secure Memory Encryption support Ingo Molnar
2017-09-04 12:23 ` Kirill A. Shutemov
2017-09-04 13:01 ` Thomas Gleixner
2017-09-04 13:54 ` Ingo Molnar
2017-09-05 21:17 ` Linus Torvalds
2017-09-05 21:37 ` Andy Lutomirski
2017-09-05 21:44 ` Borislav Petkov
2017-09-05 21:40 ` Ingo Molnar
2017-09-05 21:45 ` Linus Torvalds
2017-09-05 22:33 ` Linus Torvalds
2017-09-05 22:35 ` Andy Lutomirski
2017-09-05 23:09 ` Linus Torvalds
2017-09-06 20:43 ` Jiri Kosina
2017-09-06 21:16 ` Jiri Kosina
2017-09-06 22:26 ` Andy Lutomirski
2017-09-05 21:50 ` Linus Torvalds
2017-09-07 8:07 ` Ingo Molnar
2017-09-07 8:13 ` Ingo Molnar [this message]
2017-09-15 11:26 ` Pavel Machek
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=20170907081320.f5shfxcig734bmpd@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.