public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI: PCI Interrupt Links -- disable when unused
Date: Fri, 19 Dec 2008 12:21:19 -0800	[thread overview]
Message-ID: <494C023F.6070207@kernel.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0812191337160.3745@localhost.localdomain>


>> maybe could have one switch in /proc so could not disable that for
>> some kexec path...
> 
> I fail to comprehend the benefits of kexec,
> and the requirements that kexec puts on the kernel, other than:
> 
> # CONFIG_KEXEC is not set
> 

for me: it is a tools that i could use to make sure root-cause is in FW, and BIOS guys will not kick back the ball to os team.
after modifying table or hw reg in first kernel, and kexec even stock kernel, everything will work well.

YH

  reply	other threads:[~2008-12-19 20:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  8:22 _DIS ACPI PCI Interrupt Links Len Brown
2008-12-19  8:22 ` [PATCH 1/2] ACPI: update pci_link debug messages Len Brown
2008-12-19  8:22   ` [PATCH 2/2] ACPI: PCI Interrupt Links -- disable when unused Len Brown
2008-12-19  9:10     ` Yinghai Lu
2008-12-19  9:33       ` Len Brown
2008-12-19 11:57         ` Yinghai Lu
2008-12-19 18:39           ` Len Brown
2008-12-19 20:21             ` Yinghai Lu [this message]
2009-01-09  6:55               ` why kexec (was Re: [PATCH 2/2] ACPI: PCI Interrupt Links -- disable when unused) Len Brown
2009-01-09  7:24                 ` Yinghai Lu
2009-01-09 10:30                   ` Len Brown

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=494C023F.6070207@kernel.org \
    --to=yinghai@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.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