All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Trammell Hudson <hudson@trmm.net>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"roger.pau@citrix.com" <roger.pau@citrix.com>,
	"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
	"wl@xen.org" <wl@xen.org>
Subject: Re: [PATCH v4 3/4] efi: Enable booting unified hypervisor/kernel/initrd images
Date: Thu, 17 Sep 2020 17:10:07 +0200	[thread overview]
Message-ID: <08f957a4-3290-8ab8-1076-174f275b6f9c@suse.com> (raw)
In-Reply-To: <6Vz2rQJvGRtW6Uinda3l_V45Sor337x8uIkVphhgLRUkZSQz33lOJn-qkqwyUhtO-8ZWS28kdVrgIduNAq5Fkv0JPGbJf6_MTvlGAGRYm_s=@trmm.net>

On 17.09.2020 15:33, Trammell Hudson wrote:
> On Thursday, September 17, 2020 9:04 AM, Trammell Hudson <hudson@trmm.net> wrote:
>> On Thursday, September 17, 2020 8:33 AM, Jan Beulich jbeulich@suse.com wrote:
>>> [...]
>>>> -   if ( read_section(image, ".ucode", &ucode, NULL) )
>>>> -            return;
>>>>
>>>> -   name.s = get_value(&cfg, section, "ucode");
>>>
>>> With the Arm change already in mind and with further similar
>>> changes further down, may I suggest to consider passing
>>> 'section' into read_section(), thus guaranteeing consistent
>>> naming between image section and config file items, not only now
>>> but also going forward? read_section() would then check for the
>>> leading dot followed by the specified name.
>>
>> That could work, I think. Let me test it out for v5.
> 
> Or maybe not. section is the "section-name" of the config file
> that is being booted:
> 
> [global]
> default=section-name
> 
> Meanwhile, read_section() wants the PE section name, like ".ucode", which might appear as a line item in that section.

Oh, yes - looking at just the code fragment left in context I
realize my comment was just rubbish. Sorry.

Jan


  reply	other threads:[~2020-09-17 15:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14 11:50 [PATCH v4 0/4] efi: Unified Xen hypervisor/kernel/initrd images Trammell Hudson
2020-09-14 11:50 ` [PATCH v4 1/4] efi/boot.c: add file.need_to_free Trammell Hudson
2020-09-16  6:43   ` Roger Pau Monné
2020-09-17 11:06     ` Jan Beulich
2020-09-14 11:50 ` [PATCH v4 2/4] efi/boot.c: add handle_file_info() Trammell Hudson
2020-09-16  6:46   ` Roger Pau Monné
2020-09-17 11:29   ` Jan Beulich
2020-09-14 11:50 ` [PATCH v4 3/4] efi: Enable booting unified hypervisor/kernel/initrd images Trammell Hudson
2020-09-16  7:32   ` Roger Pau Monné
2020-09-16  8:37     ` Trammell Hudson
2020-09-16  9:47       ` Jan Beulich
2020-09-16 10:15       ` Roger Pau Monné
2020-09-17 12:33   ` Jan Beulich
2020-09-17 13:04     ` Trammell Hudson
2020-09-17 13:33       ` Trammell Hudson
2020-09-17 15:10         ` Jan Beulich [this message]
2020-09-17 15:21       ` Jan Beulich
2020-09-14 11:50 ` [PATCH v4 4/4] efi: Do not use command line if secure boot is enabled Trammell Hudson
2020-09-16  7:45   ` Roger Pau Monné
2020-09-16  8:50     ` Trammell Hudson
2020-09-16  9:57       ` Jan Beulich
2020-09-17 12:51   ` Jan Beulich
2020-09-17 14:05     ` Trammell Hudson
2020-09-17 15:26       ` Jan Beulich
2020-09-17 15:45         ` Trammell Hudson

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=08f957a4-3290-8ab8-1076-174f275b6f9c@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=hudson@trmm.net \
    --cc=roger.pau@citrix.com \
    --cc=wl@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.