On 05/09/2016 11:52 PM, Alberto Garcia wrote:
On Wed 13 Apr 2016 10:33:08 AM CEST, Changlong Xie wrote:
Sorry for the late reply!
Never mind : )
The patch looks good, I have some additional comments on top of what Max
Wrote, nothing serious though :)
@@ -67,6 +68,9 @@ typedef struct Quoru
> > Yes, I think so. However to really make good hints, upper layers would most
> > likely need more information about the exact problem with a property -
> > maybe something like an enum value per problematic property.
> > (UNAVAILABLE_FEATURE, VALUE_TOO_BIG, VALUE_TOO_SMALL, UNSUPPORTED_VALUE)
On Mon, 9 May 2016 17:32:50 +0100
"Daniel P. Berrange" wrote:
> On Mon, May 09, 2016 at 06:20:22PM +0200, Petr Tesarik wrote:
> > On Mon, 9 May 2016 17:13:07 +0100
> > "Daniel P. Berrange" wrote:
> >
> > > On Mon, May 09, 2016 at 09:52:28AM -0600, Eric Blake wrote:
> > > > On 05/07/2016 05:32 P
On Mon, May 09, 2016 at 10:37:24PM +0200, Radim Krčmář wrote:
> 2016-05-09 19:15+0200, Radim Krčmář:
> > From: =?UTF-8?q?Radim=20Kr=C4=8Dm=C3=A1=C5=99?=
> > Date: Mon, 9 May 2016 19:04:56 +0200
> > Subject: [PATCH] intel_iommu: support all masks in interrupt entry cache
> > invalidation
> >
> >
On Mon, May 09, 2016 at 01:58:48PM +0200, Paolo Bonzini wrote:
> Is this enough too?
>
> diff --git a/hw/intc/ioapic.c b/hw/intc/ioapic.c
> index 378e663..2443a35 100644
> --- a/hw/intc/ioapic.c
> +++ b/hw/intc/ioapic.c
> @@ -72,6 +72,7 @@ static void ioapic_service(IOAPICCommonState *s)
>
And this one. Thanks :)
Regards,
-Gonglei
> -Original Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Thursday, March 03, 2016 7:19 PM
> To: Gonglei (Arei); qemu-devel@nongnu.org
> Cc: qemu-triv...@nongnu.org
> Subject: Re: [PATCH 1/6] egl-helpers: fix possible reso
Hi Gerd,
Pls pick this one, thanks :)
Regards,
-Gonglei
> -Original Message-
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Sent: Thursday, March 03, 2016 7:19 PM
> To: Gonglei (Arei); qemu-devel@nongnu.org
> Cc: qemu-triv...@nongnu.org
> Subject: Re: [PATCH 3/6] spice: fix coveri
On Mon, 9 May 2016 09:52:28 -0600
Eric Blake wrote:
> On 05/07/2016 05:32 PM, Nan Li wrote:
> > When running the command "dump-guest-memory", we usually need a large space
> > of storage to save the dumpfile into disk. It costs not only much time to
> > save a file in some of hard disks, but also
From: Cole Robinson
Right now if SDL2 is installed but not SDL1, default configure will
entirely disable SDL. Check upfront for SDL2 using pkg-config, but
still prefer SDL1 if both versions are installed.
Signed-off-by: Cole Robinson
Message-id:
c9e570b5964d128a3595efe3170129a3da459776.1462557
From: "Michael S. Tsirkin"
This adds a menu item to copy current selection to clipboard.
Seems handy for copying out guest error messages.
Signed-off-by: Michael S. Tsirkin
Message-id: 1460924740-24513-1-git-send-email-...@redhat.com
[ kraxel: fix build with CONFIG_VTE=n ]
Signed-off-by: Gerd
From: Cole Robinson
VTE terminal inner-border can be NULL. The vte-0.36 (API 2.90)
code checks for the condition too so I assume it's not just a bug
Fixes a crash on Fedora 24 with gtk 3.20
Signed-off-by: Cole Robinson
Message-id:
2b2e85d403e8760ea53afd735a170500d5c17716.1462557436.git.crobi.
From: Cole Robinson
All device manager APIs are deprecated now. Much of our usage is
just to get the current pointer, so centralize that logic and use
the new seat APIs
Signed-off-by: Cole Robinson
Message-id:
d6dec24220a4e1449a0172119c10c48e145c0f6f.1462557436.git.crobi...@redhat.com
Signed-o
From: Cole Robinson
Signed-off-by: Cole Robinson
Message-id:
98e4a3b98dc824bfaff96db43b172272c780c15f.1462557436.git.crobi...@redhat.com
Signed-off-by: Gerd Hoffmann
---
configure | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/configure b/configure
index 55bd354..
From: Cole Robinson
Simplifies printing library versions, dependent on if the library
was even found
Signed-off-by: Cole Robinson
Message-id:
3c9ab16123e06bb4109771ef6ee8acd82d449ba0.1462557436.git.crobi...@redhat.com
Signed-off-by: Gerd Hoffmann
---
configure | 18 --
1 file
From: Cole Robinson
inner-border was dropped in vte API 2.91, in favor of the standard
padding style
Signed-off-by: Cole Robinson
Message-id:
60a6cdc337d611d902f53907e66a8f37ea374d65.1462557436.git.crobi...@redhat.com
[ kraxel: Fix warning with old vte version. ]
Signed-off-by: Gerd Hoffmann
From: Cole Robinson
vte >= 0.37 expores API version 2.91, which is where all the active
development is. qemu builds and runs fine with that version, so use it
if it's available.
Signed-off-by: Cole Robinson
Message-id:
b4f0375647f7b368d3dbd3834aee58cb0253566a.1462557436.git.crobi...@redhat.com
From: Cole Robinson
sdl 2.0.4 currently has a bug which causes our UI shortcuts to fire
rapidly in succession:
https://bugzilla.libsdl.org/show_bug.cgi?id=3287
It's a toss up whether ctrl+alt+f or ctrl+alt+2 will fire an
odd or even number of times, thus determining whether the action
succeed
From: Cole Robinson
Signed-off-by: Cole Robinson
Message-id:
4c464e20d69fdcf21927ceed31a8d749b4af0c49.1462557436.git.crobi...@redhat.com
Signed-off-by: Gerd Hoffmann
---
configure | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 76600f4..55bd35
From: Cole Robinson
I accidentally tried --with-sdlabi="1.0", and it failed much later in
a weird way. Instead, throw an error if the value isn't in our
whitelist.
Signed-off-by: Cole Robinson
Message-id:
60e4822e17697d257a914df03bdb9fff4b4c0490.1462557436.git.crobi...@redhat.com
Signed-off-by
Hi,
First UI pull request for 2.7. Brings a bunch of build tweaks for gtk
and sdl. Fixes the gtk 3.20 deprication warnings. Some stuff piled
up during the freeze.
please pull,
Gerd
The following changes since commit 975eb6a547f809608ccb08c221552f11af25:
Update version for v2.6.0-rc
Cc: qemu-sta...@nongnu.org
Signed-off-by: Gerd Hoffmann
Reviewed-by: Marc-André Lureau
---
include/ui/spice-display.h | 1 +
ui/spice-display.c | 30 ++
2 files changed, 31 insertions(+)
diff --git a/include/ui/spice-display.h b/include/ui/spice-display.h
in
On 05/10/2016 10:57 AM, Li Zhijian wrote:
On 05/06/2016 06:56 PM, Zhang Chen wrote:
Signed-off-by: Zhang Chen
Signed-off-by: Li Zhijian
Signed-off-by: Wen Congyang
---
include/net/net.h | 8 ++
net/filter-mirror.c | 60
net/net.c
The testsuite was the only client that attempted to reuse a
QmpOutputVisitor for a second visit after encountering an
error and/or calling qmp_output_get_qobject() on a first
visit. The next patch is about to tighten the semantics to
be one-shot usage of the visitor, like all other visitors
(which
On 05/06/2016 08:08 AM, Eric Blake wrote:
> On 05/06/2016 06:31 AM, Markus Armbruster wrote:
>>> So all that's left are the two output functions. Can we get rid
>>> of those, and make Visitor* the only public interface, rather than
>>> making every caller have to do upcasts?
>>
>> The two output
On Fri, 05/06 09:49, Kevin Wolf wrote:
> Am 05.05.2016 um 02:32 hat Fam Zheng geschrieben:
> > On Wed, 05/04 12:12, Kevin Wolf wrote:
> > > Am 19.04.2016 um 03:42 hat Fam Zheng geschrieben:
> > > > Currently we only inactivate the top BDS. Actually bdrv_inactivate
> > > > should be the opposite of
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/153 | 191 +++
tests/qemu-iotests/153.out | 241 +
tests/qemu-iotests/group | 1 +
3 files changed, 433 insertions(+)
create mode 100755 tests/qemu-iotests/153
cre
With image locking, opening /dev/null can fail when multiple tests run
in parallel (make -j2, for example). Use null-co:// as the null protocol
doesn't do image locking.
While it's arguable we could special-case /dev/null, /dev/zero,
/dev/urandom etc in raw-posix driver, it is not really necessary
Otherwise the error handling we are expceting will be masked by the
preceding image locking check, and is going to be indistinguishable
because the error messages are all the same.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/087 | 6 ++
1 file changed, 6 insertions(+)
diff --git a/tests
On 05/06/2016 06:56 PM, Zhang Chen wrote:
Signed-off-by: Zhang Chen
Signed-off-by: Li Zhijian
Signed-off-by: Wen Congyang
---
include/net/net.h | 8 ++
net/filter-mirror.c | 60
net/net.c | 56 +
The cases is about live snapshot features. Disable image locking because
otherwise a few tests are going to fail because we reuse the same images
at blockdev-add.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/085 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tests/qemu-
We should wait for the QEMU process to terminate and close the image
before we check the data.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/091 | 3 +++
tests/qemu-iotests/091.out | 1 +
2 files changed, 4 insertions(+)
diff --git a/tests/qemu-iotests/091 b/tests/qemu-iotests/091
index 3
The VM is running, qemu-io would fail the lock acquisition.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/030 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/030 b/tests/qemu-iotests/030
index 3ac2443..fa996ef 100755
--- a/tests/qemu-iotests/030
+++ b/tes
The VM is still on, the image locking check would complain.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/140 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/qemu-iotests/140 b/tests/qemu-iotests/140
index 49f9df4..3be656a 100755
--- a/tests/qemu-iotests/140
+++ b/tes
Now that test cases are covered, we can turn it on. RO (shared) lock is
disabled to allow existing libguestfs use cases (invoking QEMU for
reading image that is exclusively locked by another QEMU).
Signed-off-by: Fam Zheng
---
block.c| 7 +++
blockdev.c | 2 +-
2 files changed, 8 inserti
In sync=none the backing image of s->target is s->common.bs, which could
be exclusively locked, the image locking wouldn't work here.
Later we can update completion code to lock it after the replaced node
has dropped its lock.
Signed-off-by: Fam Zheng
---
blockdev.c | 6 ++
1 file changed,
Reviewed-by: Niels de Vos
Signed-off-by: Fam Zheng
---
block/gluster.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/block/gluster.c b/block/gluster.c
index a8aaacf..f9c5050 100644
--- a/block/gluster.c
+++ b/block/gluster.c
@@ -723,6 +723,33 @@ static int6
So the image lock won't complain.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/046 | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/tests/qemu-iotests/046 b/tests/qemu-iotests/046
index e528b67..365658e 100755
--- a/tests/qemu-iotests/046
+++ b/test
As a very special case, in sync=none mode, the source, as the backing
image of the target, will be RO opened again, which is not accepted by
image locking because the first open could be exclusive.
Signed-off-by: Fam Zheng
---
blockdev.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/b
If specified, BDRV_O_NO_LOCK flag will be set when opening the image.
Signed-off-by: Fam Zheng
---
qemu-img.c | 89 ++
1 file changed, 72 insertions(+), 17 deletions(-)
diff --git a/qemu-img.c b/qemu-img.c
index 46f2a6d..28e350c 100644
Signed-off-by: Fam Zheng
---
qemu-nbd.c| 7 ++-
qemu-nbd.texi | 2 ++
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/qemu-nbd.c b/qemu-nbd.c
index c55b40f..a675a19 100644
--- a/qemu-nbd.c
+++ b/qemu-nbd.c
@@ -95,6 +95,7 @@ static void usage(const char *name)
"Block device
Signed-off-by: Fam Zheng
---
block/raw-posix.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/block/raw-posix.c b/block/raw-posix.c
index 906d5c9..4e4d0d2 100644
--- a/block/raw-posix.c
+++ b/block/raw-posix.c
@@ -644,15 +644,7 @@ static int raw_reopen_prepare(BDRVR
Signed-off-by: Fam Zheng
---
qemu-io.c | 24 +---
1 file changed, 21 insertions(+), 3 deletions(-)
diff --git a/qemu-io.c b/qemu-io.c
index 0598251..a601fed 100644
--- a/qemu-io.c
+++ b/qemu-io.c
@@ -107,6 +107,7 @@ static void open_help(void)
" -r, -- open file read-only\n"
Signed-off-by: Fam Zheng
---
qemu-img-cmds.hx | 44 ++--
qemu-img.c | 1 +
qemu-img.texi| 3 +++
3 files changed, 26 insertions(+), 22 deletions(-)
diff --git a/qemu-img-cmds.hx b/qemu-img-cmds.hx
index e7cded6..fa87942 100644
--- a/qemu-img-cm
This takes care both the CLOEXEC flag and fd-path mapping for image
locking.
Signed-off-by: Fam Zheng
---
include/qemu/osdep.h | 1 +
util/osdep.c | 15 +++
2 files changed, 16 insertions(+)
diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
index 089c13f..8174902 100
virtlockd in libvirt locks the first byte, we lock byte 1 to avoid
the intervene.
Both file and host device protocols are covered.
Suggested-by: "Daniel P. Berrange"
Signed-off-by: Fam Zheng
---
block/raw-posix.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/block
Signed-off-by: Fam Zheng
---
block.c | 5 +
include/block/block.h | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/block.c b/block.c
index 16c7d58..bb7ebed 100644
--- a/block.c
+++ b/block.c
@@ -880,6 +880,11 @@ static int bdrv_unlock_image(BlockDriverState
They are wrappers of POSIX fcntl file locking, with the additional
interception of open/close (through qemu_open and qemu_close) to offer a
better semantics that preserves the locks across multiple life cycles of
different fds on the same file. The reason to make this semantics
change over the fcn
Block drivers can implement this new operation .bdrv_lockf to actually lock the
image in the protocol specific way.
Signed-off-by: Fam Zheng
---
block.c | 47 +++
include/block/block_int.h | 12
2 files changed, 59 insert
As parts of the transactional reopen, they are not necessary outside
block.c. Make them static.
Signed-off-by: Fam Zheng
---
block.c | 6 --
include/block/block.h | 2 --
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/block.c b/block.c
index bb7ebed..3f5369a 100
To allow overriding the default locking behavior when opening the image.
Signed-off-by: Fam Zheng
---
qapi/block-core.json | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index 1d09079..2913f3e 100644
--- a/qapi/block-core.json
Honor the locking switch specified in CLI or QMP, and set the open flags for
the image accordingly.
Signed-off-by: Fam Zheng
---
blockdev.c | 12
1 file changed, 12 insertions(+)
diff --git a/blockdev.c b/blockdev.c
index f1f520a..200fa56 100644
--- a/blockdev.c
+++ b/blockdev.c
@@
Stash the locking state into BDRVReopenState. If it was locked, unlock
in prepare, and lock it again when commit or abort.
Signed-off-by: Fam Zheng
---
block.c | 11 +++
include/block/block.h | 1 +
2 files changed, 12 insertions(+)
diff --git a/block.c b/block.c
index 3f
v4: Don't lock RO image. [Rich]
v3: Highlight is handling of image locks during close(3) and bdrv_reopen(). A
number of new patches are added consequently.
Fam Zheng (27):
block: Add BDRV_O_NO_LOCK
qapi: Add lock-image in blockdev-add options
blockdev: Add and parse "lock-image" optio
Later the block layer will automatically lock the images to avoid unexpected
concurrent accesses to the same image, which will easily corrupt the metadata
or user data, unless in some very special cases, like migration.
The exceptional cases like shared storage migration and testing should set
BDR
On Wed, 05/04 14:46, Richard W.M. Jones wrote:
> On Thu, Apr 28, 2016 at 08:57:27PM +0800, Fam Zheng wrote:
> > They are wrappers of POSIX fcntl file locking, with the additional
> > interception of open/close (through qemu_open and qemu_close) to offer a
> > better semantics that preserves the loc
> From: Paolo Bonzini [mailto:pbonz...@redhat.com]
> Subject: Re: [PATCH 0/3] memory: some little optimzation
>
>
>
> On 20/04/2016 05:34, Gonglei wrote:
> > Please see the details in each patch.
> >
> > Gonglei (3):
> > memory: drop find_ram_block()
> > exec: adjuest rcu_read_lock requiemen
qemu_ram_unset_idstr() doesn't need rcu lock anymore,
meanwhile make the range of rcu lock in
qemu_ram_set_idstr() as small as possible.
Signed-off-by: Gonglei
---
exec.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/exec.c b/exec.c
index c840bc7..117c9a8 100644
--- a/
Please see the details in each patch.
v2 -> v1:
- rework an argument's name for clearity in patch 1. [Fam]
- fix some typos in patch 2. [Fam]
- touche block->fd directly and remove the wrappers. [Paolo]
Gonglei (3):
memory: drop find_ram_block()
exec: adjust rcu_read_lock requirement
mem
On Mon, May 9, 2016 at 10:01 AM, Peter Maydell wrote:
> On 9 May 2016 at 17:58, Alistair Francis wrote:
>> I might have to look at disabling EL3 support for the ZynqMP machine
>> form the command line, as I can't boot Linux with EL3 but not EL2.
>
> I think it's worth trying to find out why this
FWIW the response from the LLVM developers:
https://llvm.org/bugs/show_bug.cgi?id=27688
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-p2v converts physical machines to virtual
On 05/09/16 18:48, Richard W.M. Jones wrote:
>
> Actually there's a rather more fundamental problem. In the current
> linuxboot_dma.c we use asm statements at the top and bottom of the
> file (outside any function). The asm statements define the header and
> what I assume is the footer of the fi
I looked at a dozen Intel CPU that have this CPUID and all of them
always had Core offset as 1 (a wasted bit when hyperthreading is
disabled) and Package offset at least 4 (wasted bits at <= 4 cores).
QEMU uses more compact IDs and it doesn't make much sense to change it
now. I keep the SMT and C
2016-05-09 19:15+0200, Radim Krčmář:
> From: =?UTF-8?q?Radim=20Kr=C4=8Dm=C3=A1=C5=99?=
> Date: Mon, 9 May 2016 19:04:56 +0200
> Subject: [PATCH] intel_iommu: support all masks in interrupt entry cache
> invalidation
>
> Linux guests do not gracefully handle cases when the invalidation mask
> the
On Mon, May 09, 2016 at 03:06:18PM +0200, David Hildenbrand wrote:
> > > > >
> > > > > Just FYI, on other architectures (e.g. s390x), other conditions (e.g.
> > > > > cpu
> > > > > generation) also define if a CPU model is runnable, so the pure
> > > > > availability of
> > > > > features does n
On Mon, May 09, 2016 at 09:20:15AM -0600, Eric Blake wrote:
> On 05/06/2016 12:11 PM, Eduardo Habkost wrote:
> > Extend query-cpu-definitions schema to allow it to return two new
> > optional fields: "runnable" and "unavailable-features".
> > "runnable" will tell if the CPU model can be run in the
Hi everyone,
A security update to the QEMU 2.5 series is now available at:
http://wiki.qemu.org/download/qemu-2.5.1.1.tar.bz2
v2.5.1.1 is now tagged in the official qemu.git repository,
and the stable-2.5 branch has been updated accordingly:
http://git.qemu.org/?p=qemu.git;a=shortlog;h=refs
On 08.05.2016 05:35, Eric Blake wrote:
> On 05/07/2016 09:16 PM, Eric Blake wrote:
>> While working on NBD, I found myself cursing the qemu-io UI for
>> not letting me test various scenarios, particularly after fixing
>> NBD to serve at byte granularity [1]. And in the process of
>> writing these
On 08.05.2016 05:16, Eric Blake wrote:
> Make it easier to test block drivers with BDRV_REQ_FUA in
> .supported_write_flags, by adding the '-f' flag to qemu-io to
> conditionally pass the flag through to specific writes ('write',
> 'write -z', 'writev', 'aio_write', 'aio_write -z'). You'll want
> t
On 05/09/2016 07:50 PM, Laszlo Ersek wrote:
Hi Marcel,
On 05/02/16 17:37, Marcel Apfelbaum wrote:
Hi,
First two patches allocate (max_reserved_ram - max_addr_cpu_addressable) range
for PCI hotplug
(for PC Machines) instead of the previous 64-bit PCI window that included only
the ranges alloca
On 08.05.2016 05:16, Eric Blake wrote:
> There's no reason to require the user to specify a flag just so
> they can pass in unaligned numbers. Keep 'read -p' and 'write -p'
> as no-ops so that I don't have to hunt down and update all users
> of qemu-io, but otherwise make their behavior default as
On 08.05.2016 05:16, Eric Blake wrote:
> The command line defaults to BDRV_O_UNMAP, but can use
> -d to reset it. Meanwhile, the 'open' subcommand was
> defaulting to no discards, with no way to set it.
>
> The command line has both -n and -tMODE to set a variety
> of cache modes, but the 'open'
On 9 May 2016 at 18:55, Peter Maydell wrote:
> On 9 May 2016 at 18:53, Stefan Weil wrote:
>> I suggest to apply this patch to 2.6, if this is still possible
>
> It is not; sorry.
Note that it's only an error if you're building with -Werror, and
releases don't default to -Werror, so users using r
Hi Daniel i dont know
from this last i have this issue other versions was building right .
im affraid i deleted the rc3 i just make a test with 2.5.1 and you can see
configure work, like was working in past.
** Attachment added: "qemu-configure"
https://bugs.launchpad.net/qemu/+bug/1579565
On 9 May 2016 at 18:53, Stefan Weil wrote:
> I suggest to apply this patch to 2.6, if this is still possible
It is not; sorry.
thanks
-- PMM
Am 09.05.2016 um 18:44 schrieb Aurelien Jarno:
> Recent versions of GCC report the following error when compiling
> target-mips/helper.c:
>
> qemu/target-mips/helper.c:542:9: warning: ‘memset’ used with length
> equal to number of elements without multiplication by element size
> [-Wmemset-e
On 05/09/2016 07:54 PM, Laszlo Ersek wrote:
On 05/02/16 17:37, Marcel Apfelbaum wrote:
In build_crs(), the calculation and merging of the ranges already happens
in 64-bit, but the entry boundaries are silently truncated to 32-bit in the
call to aml_dword_memory(). Fix it by handling the 64-bit M
Create the devices by their DeviceCreationPriority order instead
of the input order, however devices with the same priority will
be created in the same order as before.
Signed-off-by: Marcel Apfelbaum
---
vl.c | 55 ++-
1 file changed, 46 inser
This series aims to allow more devices to be used with '-device'
by sorting the devices based on a predefined creation order flag
before creating them.
Devices like IOMMU need to be created before others, so they can leverage
the DeviceCreationPriority flag introduced by the first patch to DeviceC
Some devices need to be created before others. Add a flag
to DeviceClass and the means to query it.
Signed-off-by: Marcel Apfelbaum
---
include/hw/qdev-core.h | 13 +
include/monitor/qdev.h | 1 +
qdev-monitor.c | 19 +++
3 files changed, 33 insertions(+)
di
Signed-off-by: Marcel Apfelbaum
---
hw/pci-bridge/pci_bridge_dev.c | 1 +
hw/pci-bridge/pci_expander_bridge.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/hw/pci-bridge/pci_bridge_dev.c b/hw/pci-bridge/pci_bridge_dev.c
index 7b582e9..eb552c4 100644
--- a/hw/pci-bridge/pci_bridge_de
Since Xen will correctly handle accesses to unimplemented I/O ports (by
returning all 1's for reads and ignoring writes) there is no need for
QEMU to register backgroud I/O sections.
This patch therefore adds checks to xen_io_add/del so that sections with
memory-region ops pointing at 'unassigned_
On 08.05.2016 05:16, Eric Blake wrote:
> The Usage: summary is missing several options, but rather than
> having to maintain it, it's simpler to just state [OPTIONS],
> since the options are spelled out below.
>
> Commit 499afa2 added --image-opts, but forgot to document it in
> --help. Likewise
From: Pavel Fedin
Add state information to GICv3 object structure and implement
arm_gicv3_common_reset().
This commit includes accessor functions for the fields which are
stored as bitmaps in uint32_t arrays.
Signed-off-by: Pavel Fedin
[PMM: significantly overhauled:
* Add missing qom/cpu.h i
From: Shlomo Pongratz
Implement the distributor registers of a GICv3.
Signed-off-by: Shlomo Pongratz
[PMM: significantly overhauled/rewritten:
* use the new bitmap data structures
* restructure register read/write to handle different width accesses
natively, since almost all registers are
Move the GICv3 parent_irq and parent_fiq pointers into the
GICv3CPUState structure rather than giving them their own array.
This will make it easy to assert the IRQ and FIQ lines for a
particular CPU interface without having to know or calculate
the CPU index for the GICv3CPUState we are working on
From: Shlomo Pongratz
This patch includes the device class itself, some ID register
value functions which will be needed by both distributor
and redistributor, and some skeleton functions for handling
interrupts coming in and going out, which will be filled in
in a subsequent patch.
Signed-off-b
Implement the GICv3 logic to recalculate the highest priority pending
interrupt for each CPU after some part of the GIC state has changed.
We avoid unnecessary full recalculation where possible.
Signed-off-by: Peter Maydell
---
hw/intc/arm_gicv3.c| 290 +++
The GICv3 CPU interface needs to know when the CPU it is attached
to makes an exception level or mode transition that changes the
security state, because whether it is asserting IRQ or FIQ can change
depending on these things. Provide a mechanism for letting the GICv3
device register a hook to be c
From: Shlomo Pongratz
Implement the redistributor registers of a GICv3.
Signed-off-by: Shlomo Pongratz
[PMM: significantly overhauled/rewritten:
* use the new data structures
* restructure register read/write to handle different width accesses
natively, since almost all registers are 32-bi
From: Pavel Fedin
Add state structure descriptors for the GICv3 state. We mark
the KVM GICv3 device as having a migration blocker until the
code to save and restore the state in the kernel is implemented.
Signed-off-by: Pavel Fedin
[PMM: Adjust to renamed struct fields; switched to using uint32
Implement the code which updates the GIC state when an interrupt
input into the GIC is asserted.
Signed-off-by: Peter Maydell
---
hw/intc/arm_gicv3.c| 20 +++-
hw/intc/arm_gicv3_dist.c | 21 +
hw/intc/arm_gicv3_redist.c | 21 +
hw
Implement the registers in the GICv3 CPU interface which generate
new SGI interrupts.
Signed-off-by: Peter Maydell
---
hw/intc/arm_gicv3_cpuif.c | 125 +
hw/intc/arm_gicv3_redist.c | 40 +++
hw/intc/gicv3_internal.h | 1 +
trace-event
A half-shuffle operation takes a word with zeros in the high half:
ABCD EFGH IJKL MNOP
and spreads the bits out so they are in every other bit of the word:
0A0B 0C0D 0E0F 0G0H 0I0J 0K0L 0M0N 0O0P
A half-unshuffle performs the reverse operation.
Provide functions in bitops.h w
Add the CPU interface registers which deal with acknowledging
and dismissing interrupts.
Signed-off-by: Peter Maydell
---
hw/intc/arm_gicv3_cpuif.c | 436 ++
hw/intc/gicv3_internal.h | 5 +
trace-events | 7 +
3 files changed, 448 ins
Implement the CPU interface registers for the GICv3; these are
CPU system registers, not MMIO registers.
This commit implements all the registers which are simple
accessors for GIC state, but not those which act as interfaces
for acknowledging, dismissing or generating interrupts. (Those
will be a
Define a VMSTATE_UINT64_2DARRAY macro, to go with the ones we
already have for other type sizes.
Signed-off-by: Peter Maydell
---
include/migration/vmstate.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/migration/vmstate.h b/include/migration/vmstate.h
index 84ee355..c4e38ad
Wire up the MMIO functions exposed by the distributor and the
redistributor into MMIO regions exposed by the GICv3 device.
Signed-off-by: Peter Maydell
---
hw/intc/arm_gicv3.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/hw/intc/arm_gicv3.c b/hw/intc/arm_gi
From: Pavel Fedin
This allows to override default affinity IDs on a per-machine basis, and
possibility to retrieve IDs will be used by vGICv3 live migration code.
Signed-off-by: Pavel Fedin
Signed-off-by: Peter Maydell
---
target-arm/cpu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/t
From: Pavel Fedin
This actually implements pre_save and post_load methods for in-kernel
vGICv3.
Signed-off-by: Pavel Fedin
[PMM:
* use decimal, not 0bnnn
* fixed typo in names of ICC_APR0R_EL1 and ICC_AP1R_EL1
* completely rearranged the get and put functions to read and write
the state i
The GICv3 system registers need to know if the CPU is AArch64
in EL3 or AArch32 in Monitor mode. This happens to be the first
part of the check for arm_is_secure(), so factor it out into a
new arm_is_el3_or_mon() function that the GIC can also use.
Signed-off-by: Peter Maydell
---
target-arm/cpu
1 - 100 of 309 matches
Mail list logo
