From: Josh Triplett <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>
To: Jan Beulich <JBeulich-IBi9RG/b67k@public.gmane.org>
Cc: mingo-X9Un+BFzKDI@public.gmane.org,
tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] x86/EFI: additional checks in efi_bgrt_init()
Date: Tue, 6 Nov 2012 08:16:10 -0800 [thread overview]
Message-ID: <20121106161610.GA32040@leaf> (raw)
In-Reply-To: <5099209602000078000A6B3C-ce6RLXgGx+vWGUEhTRrCg1aTQe2KTcn/@public.gmane.org>
On Tue, Nov 06, 2012 at 01:37:10PM +0000, Jan Beulich wrote:
> >>> On 06.11.12 at 13:55, Josh Triplett <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org> wrote:
> > On Tue, Nov 06, 2012 at 08:57:06AM +0000, Jan Beulich wrote:
> >> The question here is how to properly invalidate that data then:
> >> So far I was assuming that clearing the valid bit would be the way
> >> to go, as the specification says nothing on e.g. the image address
> >> being zero having any specific meaning. I need to do that in Xen,
> >> at least for the time being, as I'm not inclined to postpone
> >> indefinitely the use of boot services memory for normal memory
> >> allocations (which we would have to do if we wanted Dom0 to
> >> be able to access the image pointed to here).
> >
> > This doesn't postpone the use of boot services memory indefinitely; the
> > BGRT driver copies the image out, and the kernel then frees boot
> > services memory. That does introduce a delay in the use of boot
> > services memory, but not an indefinite one.
>
> If and when Dom0 tells the hypervisor that it's done using that
> data is unknown from the hypervisor perspective, so for Xen
> this _is_ indefinitely.
Ah, I see.
> >> I was quite bad a design decision to allow (and even suggest)
> >> the image to live in boot services memory - one can't generally
> >> expect the ACPI parser to become available in an OS before
> >> setting up memory allocation. To Linux this already has turned
> >> out to be a problem, on Xen dealing with this would turn out
> >> even more cumbersome.
> >
> > What problems has this caused?
>
> None so far - I'm trying to prevent any from occurring.
>
> Or if you're referring to my use of the term "problems" above - I
> was referring to the fact that for this very reason the treatment
> of boot services memory had to be changed in Linux.
Oh, I definitely agree about the poor design decision of putting the
image in boot services memory. I had specifically wondered what
problems had occurred in Linux and Xen due to needing the ACPI parser
before freeing boot services memory.
- Josh Triplett
next prev parent reply other threads:[~2012-11-06 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 15:26 [PATCH] x86/EFI: additional checks in efi_bgrt_init() Jan Beulich
[not found] ` <5097E8C102000078000A661B-ce6RLXgGx+vWGUEhTRrCg1aTQe2KTcn/@public.gmane.org>
2012-11-05 18:37 ` Josh Triplett
2012-11-05 18:43 ` Matthew Garrett
[not found] ` <20121105184346.GA13508-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2012-11-05 19:00 ` Josh Triplett
2012-11-06 8:57 ` Jan Beulich
[not found] ` <5098DEF202000078000A695F-ce6RLXgGx+vWGUEhTRrCg1aTQe2KTcn/@public.gmane.org>
2012-11-06 12:55 ` Josh Triplett
2012-11-06 13:37 ` Jan Beulich
[not found] ` <5099209602000078000A6B3C-ce6RLXgGx+vWGUEhTRrCg1aTQe2KTcn/@public.gmane.org>
2012-11-06 16:16 ` Josh Triplett [this message]
2012-11-07 14:48 ` Jan Beulich
[not found] ` <509A82E402000078000A6FC8-ce6RLXgGx+vWGUEhTRrCg1aTQe2KTcn/@public.gmane.org>
2012-11-07 14:52 ` Matthew Garrett
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=20121106161610.GA32040@leaf \
--to=josh-iaamlnmf4umaiuxdjuqwma@public.gmane.org \
--cc=JBeulich-IBi9RG/b67k@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-X9Un+BFzKDI@public.gmane.org \
--cc=mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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