From: David Hildenbrand <david@redhat.com>
To: "Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Björn Töpel" <bjorn@kernel.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Bin Meng" <bmeng.cn@gmail.com>,
"Weiwei Li" <liwei1518@gmail.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org,
"Atish Patra" <atishp@atishpatra.org>,
"Atish Patra" <atishp@rivosinc.com>
Cc: "Björn Töpel" <bjorn@rivosinc.com>,
"Sunil V L" <sunilvl@ventanamicro.com>,
"Santosh Mamila" <santosh.mamila@catalinasystems.io>,
"Chethan Seshadri" <Chethan.Seshadri@catalinasystems.io>,
"Sivakumar Munnangi" <siva.munnangi@catalinasystems.io>
Subject: Re: [PATCH v2 1/3] hw/riscv/virt: Add memory hotplugging and virtio-md-pci support
Date: Mon, 27 May 2024 09:19:09 +0200 [thread overview]
Message-ID: <f1fe0673-254d-494e-ba8a-d252723c1f16@redhat.com> (raw)
In-Reply-To: <18f217cf-6d68-4676-8674-d91f96e155fc@ventanamicro.com>
>
> I wonder if we should forbid users from removing memory that is 'out of place',
> i.e. users
> should always remove pc-dimms in LIFO order. Usually this kind of control is
> done by
> management, e.g. libvirt, but if we're not sure we'll keep consistency during
> memory
> unplugs ...
I really don't think we should do any of that. ;)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2024-05-27 7:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 10:56 [PATCH v2 0/3] RISC-V virt MHP support Björn Töpel
2024-05-21 10:56 ` [PATCH v2 1/3] hw/riscv/virt: Add memory hotplugging and virtio-md-pci support Björn Töpel
2024-05-24 8:53 ` Daniel Henrique Barboza
2024-05-27 11:49 ` Björn Töpel
2024-05-24 13:14 ` Daniel Henrique Barboza
2024-05-24 15:02 ` David Hildenbrand
2024-05-24 15:29 ` Daniel Henrique Barboza
2024-05-27 7:19 ` David Hildenbrand [this message]
2024-05-27 12:03 ` Björn Töpel
2024-05-27 13:19 ` Daniel Henrique Barboza
2024-05-21 10:56 ` [PATCH v2 2/3] hw/riscv/virt-acpi-build: Expose device memory in ACPI SRAT Björn Töpel
2024-05-21 10:56 ` [PATCH v2 3/3] hw/riscv/virt: Add ACPI GED and PC-DIMM MHP support Björn Töpel
2024-05-24 9:10 ` Daniel Henrique Barboza
2024-05-27 12:08 ` Björn Töpel
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=f1fe0673-254d-494e-ba8a-d252723c1f16@redhat.com \
--to=david@redhat.com \
--cc=Chethan.Seshadri@catalinasystems.io \
--cc=alistair.francis@wdc.com \
--cc=atishp@atishpatra.org \
--cc=atishp@rivosinc.com \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=santosh.mamila@catalinasystems.io \
--cc=siva.munnangi@catalinasystems.io \
--cc=sunilvl@ventanamicro.com \
--cc=zhiwei_liu@linux.alibaba.com \
/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.