public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org, acpi@linux.intel.com
Subject: Re: [PATCH] acpi: Better describe ACPI_DEBUGGER
Date: Mon, 30 Nov 2015 23:39:08 +0100	[thread overview]
Message-ID: <20151130223908.GH3816@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1645670.Yj5okVLt1U@vostro.rjw.lan>

On Mon, Nov 30, 2015 at 11:43:26PM +0100, Rafael J. Wysocki wrote:
> On Monday, November 30, 2015 10:32:15 PM Peter Zijlstra wrote:
> > Hi,
> > 
> > For a brief moment I was tricked into thinking that:
> > 
> >   In-kernel debugger (EXPERIMENTAL) (ACPI_DEBUGGER) [N/y/?] (NEW)
> > 
> > might be something useful. Better describe the feature to reduce
> > such confusion.
> > 
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> 
> Applied, thanks!
> 
> I should have caught that, sorry for the sloppiness.

n/p, for a brief moment I thought about things like a GDB stub running
in SMM -- which would be entirely awesome if it had dedicated IO through
a BMC or simple serial.

Then I thought about all the kvm-gdb-stub fail I've encountered over the
years and figured this would never work, seeing how BIOSes are never
updated/fixed.

  reply	other threads:[~2015-11-30 22:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 21:32 [PATCH] acpi: Better describe ACPI_DEBUGGER Peter Zijlstra
2015-11-30 22:43 ` Rafael J. Wysocki
2015-11-30 22:39   ` Peter Zijlstra [this message]
2015-12-01 21:45     ` Blibbet

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=20151130223908.GH3816@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acpi@linux.intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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