From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Borislav Petkov <bpetkov@suse.de>
Subject: Re: [PATCH 0/2] irqstack changes for Josh
Date: Fri, 30 Jun 2017 11:37:14 -0500 [thread overview]
Message-ID: <20170630163714.ct7rtvl6iep3jbrb@treble> (raw)
In-Reply-To: <cover.1498838018.git.luto@kernel.org>
On Fri, Jun 30, 2017 at 08:56:31AM -0700, Andy Lutomirski wrote:
> Patch 1 consolidates code and patch 2 fixes a glitch that Josh noticed.
> These could go straight to -tip, but it may make more sense for Josh
> to add them to his undwarf series.
>
> P.S. Should undwarf be called balrog instead? It seems that Josh has
> been delving very deeply indeed lately.
Who cares about that entry code stuff. I like the Balrog idea. The top
contenders in my mind are:
- Balrog unwinder
- Orc unwinder
- Undwarf unwinder
--
Josh
prev parent reply other threads:[~2017-06-30 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 15:56 Andy Lutomirski
2017-06-30 15:56 ` [PATCH 1/2] x86/entry/64: Refactor IRQ stacks and make them NMI-safe Andy Lutomirski
2017-06-30 15:56 ` [PATCH 2/2] x86/entry/64: Initialize the top of the IRQ stack before switching stacks Andy Lutomirski
2017-06-30 16:37 ` Josh Poimboeuf [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=20170630163714.ct7rtvl6iep3jbrb@treble \
--to=jpoimboe@redhat.com \
--cc=bpetkov@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.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 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®