linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Sylvain Chouleur <sylvain.chouleur@gmail.com>
Cc: linux-efi@vger.kernel.org,
	Sylvain Chouleur <sylvain.chouleur@intel.com>,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2/2] efi: implement interruptible runtime services
Date: Thu, 14 Jan 2016 16:21:42 +0000	[thread overview]
Message-ID: <20160114162142.GD3602@codeblueprint.co.uk> (raw)
In-Reply-To: <CAD_mUW3gNhWcT02b_5+mhAx764eEFVNq7EWf5TnjngSEVFFvNQ@mail.gmail.com>

On Fri, 08 Jan, at 02:57:13PM, Sylvain Chouleur wrote:
> 
> I understand, like I said above I'll modify efi_interruptible handlers to
> call legacy ones in case of panic context.
> I would like to avoid removing the panic part of this patch and take time
> to clean it before merging the whole.
 
OK, well at least split out the panic diddling into a separate patch
so that we can discuss the merits of it separately to the other, less
contentious changes.

> > Kconfig is a last resort because it's a build-time decision and
> > greatly limits the flexibility of the kernel. It becomes no longer
> > possible to run a single kernel image with various CONFIG_* enabled on
> > x86 hardware - you now need a special EFI_INTERRUPTIBLE build.
> >
> > Which apart from being a major headache for distributions in general
> > is generally frowned upon for the x86 architecture.
> >
> > If there's any way at all of making this a runtime decision that would
> > be much better.
> 
> I think the best would be to bind this driver with the one which receives the
> interrupts from CSE to write the variables. Then we would have a consistency
> on the feature.
> Does this seems ok for you?

I think that'd be an improvement, yeah.

  reply	other threads:[~2016-01-14 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1450434591-31104-1-git-send-email-sylvain.chouleur@gmail.com>
     [not found] ` <1450434591-31104-2-git-send-email-sylvain.chouleur@gmail.com>
2016-01-06 12:58   ` [PATCH 2/2] efi: implement interruptible runtime services Matt Fleming
2016-01-06 15:57     ` Sylvain Chouleur
2016-01-08 10:38       ` Matt Fleming
2016-01-08 13:57         ` Sylvain Chouleur
2016-01-14 16:21           ` Matt Fleming [this message]
2016-01-06 22:33 ` [PATCH v2 0/3] efi " Sylvain Chouleur
2016-01-06 22:33   ` [PATCH v2 3/3] efi: implement " Sylvain Chouleur
2016-01-13 16:32   ` [PATCH v3 0/3] efi " Sylvain Chouleur
2016-01-13 16:32     ` [PATCH v3 3/3] efi: implement " Sylvain Chouleur
2016-02-11 14:19       ` Matt Fleming
2016-02-11 14:23         ` Sylvain Chouleur

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=20160114162142.GD3602@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=sylvain.chouleur@gmail.com \
    --cc=sylvain.chouleur@intel.com \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).