All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Igor Druzhinin <igor.druzhinin@citrix.com>
Cc: xen-devel@lists.xenproject.org, andrew.cooper3@citrix.com,
	roger.pau@citrix.com, wl@xen.org, iwj@xenproject.org
Subject: Re: [PATCH v2.1] hvmloader: indicate dynamically allocated memory as ACPI NVS in e820
Date: Fri, 4 Sep 2020 17:29:02 +0200	[thread overview]
Message-ID: <b1d7655a-5aed-2930-7141-0a360da48ed4@suse.com> (raw)
In-Reply-To: <885f0f9b-14d1-3246-1d5b-a60356fb42f2@citrix.com>

On 04.09.2020 16:47, Igor Druzhinin wrote:
> The referenced commit is not unrelated - it's the commit introducing the access
> causing kexec transition to fail. But I can add another one pointing to the mapping
> of ACPI tables that was supposed to fix the failure caused by the first one.

Oh, okay, I finally understand. The purpose of the change is
unrelated, it's what get_acpi_srat_table() does which causes the
problem. Hopefully this will be more obvious with the other commit
also referenced. How about additionally changing "which is now a
requirement after" to "which is now a requirement in order for ...
to work" or "which is a prerequisite for ... actually functioning"
or some such?

Jan


      reply	other threads:[~2020-09-04 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01  2:50 [PATCH v2.1] hvmloader: indicate dynamically allocated memory as ACPI NVS in e820 Igor Druzhinin
2020-09-01  9:28 ` Roger Pau Monné
2020-09-01 10:29   ` Igor Druzhinin
2020-09-04  8:33 ` Jan Beulich
2020-09-04 11:49   ` Igor Druzhinin
2020-09-04 14:40     ` Jan Beulich
2020-09-04 14:47       ` Igor Druzhinin
2020-09-04 15:29         ` Jan Beulich [this message]

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=b1d7655a-5aed-2930-7141-0a360da48ed4@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=igor.druzhinin@citrix.com \
    --cc=iwj@xenproject.org \
    --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.