All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Leo Yan <leo.yan@linaro.org>
Cc: Ard Biesheuvel <ardb@kernel.org>, Julien Grall <julien@xen.org>,
	Jan Beulich <jbeulich@suse.com>,
	Bertrand Marquis <Bertrand.Marquis@arm.com>,
	Rahul Singh <Rahul.Singh@arm.com>,
	Peter Griffin <peter.griffin@linaro.org>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Julien Grall <jgrall@amazon.com>,
	Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: Re: [PATCH] xen/arm: acpi: Support memory reserve configuration table
Date: Tue, 06 Sep 2022 09:28:10 +0100	[thread overview]
Message-ID: <87ilm0rjol.wl-maz@kernel.org> (raw)
In-Reply-To: <Yxb2c6aLrcf8e16q@leoy-huanghe.lan>

On Tue, 06 Sep 2022 08:27:47 +0100,
Leo Yan <leo.yan@linaro.org> wrote:
> 
> On Tue, Sep 06, 2022 at 09:22:00AM +0200, Ard Biesheuvel wrote:
> 
> [...]
> 
> > > IIUC, you consider the general flow from architecture view, so you prefer
> > > to ask Xen to implement EFI stub to comply the general flow for EFI
> > > booting sequence, right?
> > >
> > > If the conclusion is to change Xen for support EFI stub, then this
> > > would be fine for me and I will hold on and leave Xen developers to work
> > > on it.
> > >
> > 
> > As I mentioned before, proper EFI boot support in Xen would be nice.
> > *However*, I don't think it makes sense to go through all the trouble
> > of implementing that just to shut up a warning that doesn't affect Xen
> > to begin with.
> 
> Another option is we can set a bit for xen feature, so Linux kernel
> can read out the xen feature and make decision if need to reserve
> memory for RD tables based on the new feature bit.  This is somehow
> a solution is to create a general protocol between Xen and Linux kernel.
> 
> How about you think for this?

No. If there is such a bit, it has to be in the GIC architecture. I'm
not putting anything hypervisor-specific into the GIC driver. Others
have tried before you, and they ended up fixing their hypervisor
instead.

Feel free to talk to ARM to get the architecture updated instead.

	M.

-- 
Without deviation from the norm, progress is not possible.


  parent reply	other threads:[~2022-09-06 21:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 10:57 [PATCH] xen/arm: acpi: Support memory reserve configuration table Leo Yan
2022-08-17 13:17 ` Jan Beulich
2022-08-17 13:49   ` Ard Biesheuvel
2022-08-18  9:15     ` Leo Yan
2022-08-18  9:33       ` Ard Biesheuvel
2022-08-18 10:04         ` Julien Grall
2022-08-18 15:49           ` Leo Yan
2022-08-18 16:24             ` Ard Biesheuvel
2022-08-19 12:10               ` Marc Zyngier
2022-08-25  7:59                 ` Leo Yan
2022-08-25  9:07                   ` Julien Grall
2022-08-25 11:24                     ` Leo Yan
2022-08-25 12:51                       ` Julien Grall
2022-08-25 11:50                     ` Leo Yan
2022-08-25 12:59                       ` Julien Grall
2022-08-25 14:40                         ` Leo Yan
2022-09-06  2:52                           ` Leo Yan
2022-09-06  6:27                             ` Marc Zyngier
2022-09-06  7:17                               ` Leo Yan
2022-09-06  7:22                                 ` Ard Biesheuvel
2022-09-06  7:27                                   ` Leo Yan
2022-09-06  7:43                                     ` Leo Yan
2022-09-06  8:28                                     ` Marc Zyngier [this message]
2022-09-06  7:53                                 ` Marc Zyngier
2022-09-06 15:13                                   ` Leo Yan
2022-09-06 15:18                                     ` Marc Zyngier
2022-08-18  9:40       ` Marc Zyngier
2022-08-18  7:34   ` Leo Yan
2022-08-18  7:47     ` Jan Beulich
2022-08-18  8:46       ` Leo Yan
2022-08-18  8:52         ` Jan Beulich
2022-08-18  7:57     ` Julien Grall
2022-08-18  8:28       ` Leo Yan
2022-08-18 13:24       ` Bertrand Marquis

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=87ilm0rjol.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=Bertrand.Marquis@arm.com \
    --cc=Rahul.Singh@arm.com \
    --cc=ardb@kernel.org \
    --cc=jbeulich@suse.com \
    --cc=jgrall@amazon.com \
    --cc=julien@xen.org \
    --cc=leo.yan@linaro.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=peter.griffin@linaro.org \
    --cc=xen-devel@lists.xenproject.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.