All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Juergen Gross <jgross@suse.com>
Cc: sstabellini@kernel.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	mingo@redhat.com, bp@alien8.de, hpa@zytor.com,
	xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
	tglx@linutronix.de
Subject: Re: [Xen-devel] [PATCH v2 1/2] x86: respect memory size limiting via mem= parameter
Date: Mon, 11 Feb 2019 13:23:08 +0100	[thread overview]
Message-ID: <20190211122308.GA119972@gmail.com> (raw)
In-Reply-To: <bd5863a2-291a-43e5-7633-c84c1026a31b@suse.com>


* Juergen Gross <jgross@suse.com> wrote:

> > If PCI devices had physical mmio memory areas above this range, we'd 
> > still expect them to work - the option was really only meant to limit 
> > RAM.
> 
> No, in this case it seems to be real RAM added via PCI. The RAM is 
> initially present in the E820 map, but the "mem=" will remove it from 
> there again. During ACPI scan it is found (again) and will be added via 
> hotplug mechanism, so "mem=" has no effect for that memory.

OK. With that background:

Acked-by: Ingo Molnar <mingo@kernel.org>

I suppose you want this to go upstream via the Xen tree, which is the 
main testcase for the bug to begin with?

Thanks,

	ngo


  reply	other threads:[~2019-02-11 12:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  8:22 [PATCH v2 0/2] x86: respect memory size limits Juergen Gross
2019-01-30  8:22 ` [PATCH v2 1/2] x86: respect memory size limiting via mem= parameter Juergen Gross
2019-01-30  8:22 ` Juergen Gross
2019-02-11 12:06   ` Ingo Molnar
2019-02-11 12:06   ` Ingo Molnar
2019-02-11 12:14     ` Juergen Gross
2019-02-11 12:14     ` [Xen-devel] " Juergen Gross
2019-02-11 12:23       ` Ingo Molnar [this message]
2019-02-11 12:35         ` Juergen Gross
2019-02-11 12:35         ` Juergen Gross
2019-02-11 12:23       ` Ingo Molnar
2019-01-30  8:22 ` [PATCH v2 2/2] x86/xen: dont add memory above max allowed allocation Juergen Gross
2019-01-30  8:22 ` Juergen Gross
2019-01-30 10:59   ` William Kucharski
2019-01-30 10:59   ` William Kucharski
2019-02-01 18:46   ` Boris Ostrovsky
2019-02-07  6:32     ` Juergen Gross
2019-02-07  6:32     ` Juergen Gross
2019-02-01 18:46   ` Boris Ostrovsky

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=20190211122308.GA119972@gmail.com \
    --to=mingo@kernel.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=sstabellini@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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.