From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Xiao Guangrong <guangrong.xiao@linux.intel.com>,
pbonzini@redhat.com, ehabkost@redhat.com, kvm@vger.kernel.org,
gleb@kernel.org, mtosatti@redhat.com, qemu-devel@nongnu.org,
stefanha@redhat.com, dan.j.williams@intel.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v3 0/4] nvdimm: hotplug support
Date: Thu, 3 Nov 2016 06:53:33 +0200 [thread overview]
Message-ID: <20161103065256-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20161102150133.043b4923@nial.brq.redhat.com>
On Wed, Nov 02, 2016 at 03:01:33PM +0100, Igor Mammedov wrote:
> On Sat, 29 Oct 2016 00:35:36 +0800
> Xiao Guangrong <guangrong.xiao@linux.intel.com> wrote:
>
> > It is based on my previous patchset,
> > "[PATCH 0/8] nvdimm acpi: bug fix and cleanup", these two patchset are
> > against commit dea651a95af6dad099 (intel-iommu: Check IOAPIC's Trigger Mode
> > against the one in IRTE) on pci branch of Michael's git tree and can be
> > found at:
> > https://github.com/xiaogr/qemu.git nvdimm-hotplug-v3
> >
> > Changelog in v3:
> > 1) use a dedicated interrupt for nvdimm device hotplug
> > 2) stop nvdimm device hot unplug
> > 3) reserve UUID and handle for QEMU internally used QEMU
> > 5) redesign fit buffer to avoid OSPM reading incomplete fit info
> > 6) bug fixes and cleanups
> >
> > Changelog in v2:
> > Fixed signed integer overflow pointed out by Stefan Hajnoczi
> >
> > This patchset enables nvdimm hotplug support, it is used as pc-dimm hotplug,
> > for example, a new nvdimm device can be plugged as follows:
> > object_add memory-backend-file,id=mem3,size=10G,mem-path=/home/eric/nvdimm3
> > device_add nvdimm,id=nvdimm3,memdev=mem3
> >
> > and unplug it as follows:
> > device_del nvdimm3
> > object_del mem3
> there is no unplug support
>
>
> instead of incremental fixups on top merged patches in followup series,
> I'd prefer it to make a clean revert for patches 2-4/4 first and
> them amended versions of them to follow.
Let's get the fixes reviewed first, how to apply them is
a minor issue in my eyes.
> >
> > Xiao Guangrong (4):
> > nvdimm acpi: prebuild nvdimm devices for available slots
> > nvdimm acpi: introduce fit buffer
> > nvdimm acpi: introduce _FIT
> > pc: memhp: enable nvdimm device hotplug
> >
> > docs/specs/acpi_mem_hotplug.txt | 3 +
> > docs/specs/acpi_nvdimm.txt | 58 ++++++-
> > hw/acpi/memory_hotplug.c | 31 +++-
> > hw/acpi/nvdimm.c | 286 +++++++++++++++++++++++++++++++----
> > hw/core/hotplug.c | 11 ++
> > hw/core/qdev.c | 20 ++-
> > hw/i386/acpi-build.c | 9 +-
> > hw/i386/pc.c | 31 ++++
> > hw/mem/nvdimm.c | 4 -
> > include/hw/acpi/acpi_dev_interface.h | 1 +
> > include/hw/hotplug.h | 10 ++
> > include/hw/mem/nvdimm.h | 27 +++-
> > 12 files changed, 443 insertions(+), 48 deletions(-)
> >
next prev parent reply other threads:[~2016-11-03 4:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 16:35 [PATCH v3 0/4] nvdimm: hotplug support Xiao Guangrong
2016-10-28 16:35 ` [PATCH v3 1/4] nvdimm acpi: prebuild nvdimm devices for available slots Xiao Guangrong
2016-11-01 15:16 ` Igor Mammedov
2016-10-28 16:35 ` [PATCH v3 2/4] nvdimm acpi: introduce fit buffer Xiao Guangrong
2016-11-01 15:17 ` Stefan Hajnoczi
2016-11-01 15:25 ` Igor Mammedov
2016-11-01 16:00 ` Xiao Guangrong
2016-10-28 16:35 ` [PATCH v3 3/4] nvdimm acpi: introduce _FIT Xiao Guangrong
2016-11-01 16:24 ` Igor Mammedov
2016-11-02 15:40 ` Xiao Guangrong
2016-11-03 9:15 ` Igor Mammedov
2016-11-01 16:41 ` Stefan Hajnoczi
2016-11-02 15:42 ` Xiao Guangrong
2016-11-02 13:56 ` [Qemu-devel] " Igor Mammedov
2016-11-02 15:54 ` Xiao Guangrong
2016-11-03 9:22 ` Igor Mammedov
2016-10-28 16:35 ` [PATCH v3 4/4] pc: memhp: enable nvdimm device hotplug Xiao Guangrong
2016-11-01 16:44 ` Stefan Hajnoczi
2016-11-02 11:21 ` Igor Mammedov
2016-11-02 15:55 ` Xiao Guangrong
2016-11-02 14:01 ` [Qemu-devel] [PATCH v3 0/4] nvdimm: hotplug support Igor Mammedov
2016-11-03 4:53 ` Michael S. Tsirkin [this message]
2016-11-03 9:27 ` Igor Mammedov
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=20161103065256-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=ehabkost@redhat.com \
--cc=gleb@kernel.org \
--cc=guangrong.xiao@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox