From: Jan Kiszka <jan.kiszka@siemens.com>
To: Liu Yu-B13201 <Yu.Liu@freescale.com>
Cc: qemu-devel@nongnu.org, kvm-ppc@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 4/7] kvm: Add sanity checks to slot management
Date: Wed, 29 Apr 2009 12:38:01 +0200 [thread overview]
Message-ID: <49F82E09.3070702@siemens.com> (raw)
In-Reply-To: <0A1FE637C2C7E148B9573BB60CC630E5210713@zch01exm26.fsl.freescale.net>
Liu Yu-B13201 wrote:
>
>> -----Original Message-----
>> From: qemu-devel-bounces+yu.liu=freescale.com@nongnu.org
>> [mailto:qemu-devel-bounces+yu.liu=freescale.com@nongnu.org]
>> On Behalf Of Jan Kiszka
>> Sent: Sunday, April 12, 2009 1:20 AM
>> To: qemu-devel@nongnu.org
>> Subject: [Qemu-devel] [PATCH 4/7] kvm: Add sanity checks to
>> slot management
>>
>> Fail loudly if we run out of memory slot.
>>
>> Make sure that dirty log start/stop works with consistent
>> memory regions
>> by reporting invalid parameters. This reveals several
>> inconsistencies in
>> the vga code, patch to fix them follows later in this series.
>>
>> And, for simplicity reasons, also catch and report unaligned memory
>> regions passed to kvm_set_phys_mem (KVM works on page basis).
>>
>
> Commit d3f8d37fe2d0c24ec8bac9c94d5b0e2dc09c0d2a hurts kvm/powerpc
> The alignment check in kvm_set_phys_mem prevents pci controller and mpic initializing mmio regions.
What is the alignment of those regions then? None? And do regions of
different types overlap even on the same page? Maybe the check reveals
some deeper conflict /wrt KVM. Can you point me to the involved code files?
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-04-29 10:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-11 17:20 [Qemu-devel] [PATCH 0/7] kvm: fix system reset & rework slot management Jan Kiszka
2009-04-11 17:20 ` [Qemu-devel] [PATCH 6/7] vga: Fix inconsistent tracking of map_addr Jan Kiszka
2009-04-11 17:20 ` [Qemu-devel] [PATCH 5/7] kvm: improve handling of overlapping slots Jan Kiszka
2009-04-13 11:00 ` [Qemu-devel] [PATCH 5/7 v2] " Jan Kiszka
2009-04-17 14:36 ` Anthony Liguori
2009-04-11 17:20 ` [Qemu-devel] [PATCH 2/7] kvm: Apply SMM-already-initialized workaround on reset Jan Kiszka
2009-04-11 17:20 ` [Qemu-devel] [PATCH 1/7] kvm: Sync CPU state " Jan Kiszka
2009-04-17 14:26 ` Anthony Liguori
2009-04-11 17:20 ` [Qemu-devel] [PATCH 4/7] kvm: Add sanity checks to slot management Jan Kiszka
2009-04-29 10:31 ` Liu Yu-B13201
2009-04-29 10:38 ` Jan Kiszka [this message]
2009-04-29 11:10 ` Liu Yu-B13201
2009-04-29 11:36 ` Jan Kiszka
2009-04-29 17:10 ` Hollis Blanchard
2009-04-29 17:30 ` Jan Kiszka
2009-04-29 17:37 ` Hollis Blanchard
2009-04-29 18:08 ` Jan Kiszka
2009-04-30 2:39 ` Liu Yu-B13201
2009-04-29 17:38 ` Anthony Liguori
2009-04-29 18:02 ` Hollis Blanchard
2009-04-29 18:54 ` Blue Swirl
2009-04-11 17:20 ` [Qemu-devel] [PATCH 7/7] vga: Cleanup dirty logging Jan Kiszka
2009-04-11 17:20 ` [Qemu-devel] [PATCH 3/7] kvm: Cleanup unmap condition in kvm_set_phys_mem Jan Kiszka
2009-04-17 14:27 ` [Qemu-devel] [PATCH 0/7] kvm: fix system reset & rework slot management Anthony Liguori
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=49F82E09.3070702@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Yu.Liu@freescale.com \
--cc=kvm-ppc@vger.kernel.org \
--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).