All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Julien Grall <julien@xen.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	 Henry Wang <Henry.Wang@arm.com>,
	 "xen-devel@lists.xenproject.org"
	<xen-devel@lists.xenproject.org>,
	 Bertrand Marquis <Bertrand.Marquis@arm.com>,
	Wei Chen <Wei.Chen@arm.com>,
	 Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH 2/2] xen/arm: Handle reserved heap pages in boot and heap allocator
Date: Thu, 1 Sep 2022 18:50:55 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2209011849040.3931@ubuntu-linux-20-04-desktop> (raw)
In-Reply-To: <fc0706f6-7635-6b0d-811a-c3ed41f481fc@xen.org>

On Thu, 1 Sep 2022, Julien Grall wrote:
> Hi Stefano,
> 
> On 01/09/2022 18:08, Stefano Stabellini wrote:
> > > > Also, what happen with UEFI? Is it easy to guarantee the region will not
> > > > be used?
> > > 
> > > For now I think it is not easy to guarantee that, do you have some ideas
> > > in mind? I think I can follow this in above follow-up series to improve
> > > things.
> > 
> > For clarity, are we worried that the region is used by the bootloader
> > for other things? For instance U-Boot or Tianocore placing some
> > firmware tables inside the range specified for xenheap?
> 
> Yes. I think it would be difficult for an admin to figure out which regions
> are used. Although they are likely (?) going to be static for a given
> UEFI/U-boot build.
> 
> My major concern is such bug can be very difficult to root cause because we
> have no safety in Xen. The most likely symptom would be random corruption.

Thanks for the clarification. Yeah, I think we'll have to do some
"creative thinking" to figure out a solution to this issue. I wonder if
U-boot or Tianocore have some sort of API (or build-time data) to know
the unavailable ranges.

In any case, I think we can postpone to after the release.


  reply	other threads:[~2022-09-02  1:51 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  7:31 [PATCH 0/2] Introduce reserved heap Henry Wang
2022-08-24  7:31 ` [PATCH 1/2] docs, xen/arm: Introduce reserved heap memory Henry Wang
2022-08-24 13:46   ` Michal Orzel
2022-08-25  1:04     ` Henry Wang
2022-08-30  0:47       ` Stefano Stabellini
2022-08-30  0:58         ` Henry Wang
2022-08-30  6:29           ` Michal Orzel
2022-08-30  7:10             ` Michal Orzel
2022-08-30  7:21               ` Henry Wang
2022-08-30  0:45   ` Stefano Stabellini
2022-08-30  1:02     ` Henry Wang
2022-09-01 14:36   ` Julien Grall
2022-09-02  1:28     ` Henry Wang
2022-09-02  8:01       ` Julien Grall
2022-09-02  8:21         ` Henry Wang
2022-08-24  7:31 ` [PATCH 2/2] xen/arm: Handle reserved heap pages in boot and heap allocator Henry Wang
2022-08-25 11:24   ` Michal Orzel
2022-08-30  6:11     ` Henry Wang
2022-08-30  7:19       ` Michal Orzel
2022-08-30  8:00         ` Henry Wang
2022-08-30  8:48           ` Michal Orzel
2022-08-30  9:17             ` Henry Wang
2022-08-30  9:48               ` Michal Orzel
2022-08-30 10:04                 ` Henry Wang
2022-08-30 17:28                   ` Stefano Stabellini
2022-08-31  1:36                     ` Henry Wang
2022-08-30 17:32           ` Stefano Stabellini
2022-09-01  1:03         ` Henry Wang
2022-09-01 13:31           ` Bertrand Marquis
2022-09-01 13:52             ` Henry Wang
2022-08-30  1:04   ` Stefano Stabellini
2022-08-30  8:27     ` Henry Wang
2022-08-30 17:25       ` Stefano Stabellini
2022-08-31  1:24         ` Henry Wang
2022-08-31  2:00           ` Henry Wang
2022-08-31 22:58           ` Stefano Stabellini
2022-09-01  0:49             ` Henry Wang
2022-09-01 13:58     ` Julien Grall
2022-09-01 14:01       ` Henry Wang
2022-09-01 14:02         ` Julien Grall
2022-09-01 15:29   ` Julien Grall
2022-09-01 16:05     ` Henry Wang
2022-09-01 17:08       ` Stefano Stabellini
2022-09-01 17:34         ` Julien Grall
2022-09-02  1:50           ` Stefano Stabellini [this message]
2022-09-02  3:02             ` Wei Chen
2022-09-02  3:07               ` Wei Chen
2022-09-02  8:04                 ` Julien Grall
2022-09-02  9:49                   ` Wei Chen
2022-09-01 17:19       ` Julien Grall
2022-09-02  3:30         ` Henry Wang
2022-09-02  8:11           ` Julien Grall
2022-09-02  8:18             ` Henry Wang

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=alpine.DEB.2.22.394.2209011849040.3931@ubuntu-linux-20-04-desktop \
    --to=sstabellini@kernel.org \
    --cc=Bertrand.Marquis@arm.com \
    --cc=Henry.Wang@arm.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=Wei.Chen@arm.com \
    --cc=julien@xen.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.