From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: pkrempa@redhat.com, ehabkost@redhat.com, mst@redhat.com,
bharata@linux.vnet.ibm.com, pbonzini@redhat.com,
david@gibson.dropbear.id.au
Subject: [Qemu-devel] [PATCH 0/2] ps: memhp: enforce gaps between DIMMs
Date: Fri, 25 Sep 2015 15:53:10 +0200 [thread overview]
Message-ID: <1443189192-108681-1-git-send-email-imammedo@redhat.com> (raw)
it's a simplier way suggested by Michael S. Tsirkin
to workaround virtio bug reported earlier:
http://lists.nongnu.org/archive/html/qemu-devel/2015-08/msg00522.html
where virtio can't handle buffer that crosses border
between 2 DIMM's (i.e. 2 MemoryRegions).
idea is to leave gaps between DIMMs, making their GPAs
non contiguous, which effectively forces kmalloc
to not use DIMM if buffer doesn't fit inside of it.
Igor Mammedov (2):
memhp: extend address auto assignment to support gaps
pc: memhp: force gaps between DIMM's GPA
hw/i386/pc.c | 4 +++-
hw/i386/pc_piix.c | 3 +++
hw/i386/pc_q35.c | 3 +++
hw/mem/pc-dimm.c | 13 +++++++------
hw/ppc/spapr.c | 2 +-
include/hw/i386/pc.h | 2 ++
include/hw/mem/pc-dimm.h | 7 ++++---
7 files changed, 23 insertions(+), 11 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-09-25 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 13:53 Igor Mammedov [this message]
2015-09-25 13:53 ` [Qemu-devel] [PATCH 1/2] memhp: extend address auto assignment to support gaps Igor Mammedov
2015-09-25 13:53 ` [Qemu-devel] [PATCH 2/2] pc: memhp: force gaps between DIMM's GPA Igor Mammedov
2015-09-27 10:48 ` Michael S. Tsirkin
2015-09-27 13:06 ` Igor Mammedov
2015-09-27 13:11 ` Michael S. Tsirkin
2015-09-27 14:04 ` Igor Mammedov
2015-09-27 14:18 ` Michael S. Tsirkin
2015-09-28 9:18 ` Igor Mammedov
2015-09-28 4:39 ` Bharata B Rao
2015-09-28 9:13 ` Igor Mammedov
2015-10-05 8:44 ` Bharata B Rao
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=1443189192-108681-1-git-send-email-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=ehabkost@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).