On Apr 25, 2017, at 9:16 AM, Eric Blake wrote:
On 04/24/2017 10:17 PM, G 3 wrote:
Add the ppc.risu file. It defines the format for various PowerPC
instructions.
Your emails are missing In-Reply-To and References headers, which
means
you posted 10 top-level threads instead of 9 replies to
On Wed, Mar 22, 2017 at 02:32:30PM +0100, Igor Mammedov wrote:
> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> index 0cbcbc1..8748d25 100644
> --- a/hw/arm/virt.c
> +++ b/hw/arm/virt.c
> @@ -1554,6 +1554,16 @@ static void virt_set_gic_version(Object *obj, const
> char *value, Error **errp)
> }
Hi; a recent travis build failure made me notice that our .travis.yml
config references a preseed tarball from here:
http://people.linaro.org/~alex.bennee/qemu-submodule-git-seed.tar.xz
I think this is a bit less than ideal -- we should really be hosting
this on qemu.org. Can we arrange to move it
On 04/25/2017 04:18 PM, Stafford Horne wrote:
On Tue, Apr 25, 2017 at 12:11:00PM +0200, Richard Henderson wrote:
On 04/23/2017 11:54 PM, Stafford Horne wrote:
The OpenRISC architecture has the Power Management Register (PMR)
special purpose register to manage cpu power states. The interesting
On 21 April 2017 at 09:28, Mark Cave-Ayland
wrote:
> As all surfaces in QEMU are now either shared or 32-bit ARGB regardless of
> the guest depth, remove all non-32-bit primitives from tcx_update_display()
> and consequence their implementation which are no longer required.
>
> Signed-off-by: Mark
On 21 April 2017 at 09:28, Mark Cave-Ayland
wrote:
> This was an artifact from very early versions of the code from before the
> memory API and is no longer needed.
>
> Signed-off-by: Mark Cave-Ayland
> Reviewed-by: Gerd Hoffmann
> ---
> hw/display/cg3.c |6 ++
> 1 file changed, 2 inser
On Tue, Apr 25, 2017 at 03:51:17PM +0100, Peter Maydell wrote:
> Hi; a recent travis build failure made me notice that our .travis.yml
> config references a preseed tarball from here:
> http://people.linaro.org/~alex.bennee/qemu-submodule-git-seed.tar.xz
>
> I think this is a bit less than ideal -
On 11 April 2017 at 13:26, Fam Zheng wrote:
> bdrv_inc_in_flight and bdrv_dec_in_flight are mandatory for
> BDRV_POLL_WHILE to work, even for the shortcut case where flush is
> unnecessary. Move the if block to below bdrv_dec_in_flight, and BTW fix
> the variable declaration position.
>
> Signed-o
On 04/24/17 22:45, Igor Mammedov wrote:
> Since 2.7 commit (b2a575a Add optionrom compatible with fw_cfg DMA version)
> regressed migration during firmware exection time by
> abusing fwcfg.dma_enabled property to decide loading
> dma version of option rom AND by mistake disabling DMA
> for 2.6 and
On 25 April 2017 at 15:07, Thomas Huth wrote:
> So another idea: Could you start the test in verbose mode like this:
>
> V=2 QTEST_QEMU_BINARY=aarch64-softmmu/qemu-system-aarch64 tests/test-hmp
manooth$ V=2 QTEST_QEMU_BINARY='aarch64-softmmu/qemu-system-aarch64'
tests/test-hmp
/aarch64/hmp/n810:
On Tue, 25 Apr 2017 16:48:30 +0200
Andrew Jones wrote:
> On Wed, Mar 22, 2017 at 02:32:30PM +0100, Igor Mammedov wrote:
> > diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> > index 0cbcbc1..8748d25 100644
> > --- a/hw/arm/virt.c
> > +++ b/hw/arm/virt.c
> > @@ -1554,6 +1554,16 @@ static void virt_set_
On 25 April 2017 at 16:05, Peter Maydell wrote:
> info jit
> qemu: qemu_mutex_lock: Invalid argument
Repro without the qtest machinery:
$ lldb -- ./aarch64-softmmu/qemu-system-aarch64 -M n810 -s -S -monitor
stdio -machine accel=qtest
then run and type 'info jit' at the monitor prompt.
B
Peter Maydell writes:
> Hi; a recent travis build failure made me notice that our .travis.yml
> config references a preseed tarball from here:
> http://people.linaro.org/~alex.bennee/qemu-submodule-git-seed.tar.xz
>
> I think this is a bit less than ideal -- we should really be hosting
> this on
Hi Kevin,
This happens both on master and on your block-next tree:
$ qemu-io -f raw null-co:// -c 'reopen -r'
Unexpected error in bdrv_check_perm() at /stor/work/qemu/block.c:1437:
Block node is read-only
Aborted
It seems bs->read_only and perms go out of sync when bdrv_reopen()
Am 10.04.2017 um 17:05 hat Fam Zheng geschrieben:
> bdrv_inc_in_flight and bdrv_dec_in_flight are mandatory for
> BDRV_POLL_WHILE to work, even for the shortcut case where flush is
> unnecessary. Move the if block to below bdrv_dec_in_flight, and BTW fix
> the variable declaration position.
>
> Si
On 25/04/2017 12:24, Juan Quintela wrote:
> This way we use the "normal" way of printing errors for hmp commands.
>
> --
> Paolo suggestion
"Suggested-by" tag?
>
> Signed-off-by: Juan Quintela
> ---
> hmp.c| 9 +++--
> include/sysemu/sysemu.h | 4 ++--
> migration/s
Daniel P. Berrange writes:
> On Tue, Apr 25, 2017 at 03:51:17PM +0100, Peter Maydell wrote:
>> Hi; a recent travis build failure made me notice that our .travis.yml
>> config references a preseed tarball from here:
>> http://people.linaro.org/~alex.bennee/qemu-submodule-git-seed.tar.xz
>>
>> I t
On Tue, 25 Apr 2017 17:01:21 +0200
Laszlo Ersek wrote:
> On 04/24/17 22:45, Igor Mammedov wrote:
> > Since 2.7 commit (b2a575a Add optionrom compatible with fw_cfg DMA version)
> > regressed migration during firmware exection time by
> > abusing fwcfg.dma_enabled property to decide loading
> > dm
Paolo Bonzini writes:
> On 11/04/2017 18:50, Alex Bennée wrote:
>> This can be pre-processed later from the trace file.
>
> What about skipping this patch, and instead adding five trace points
>
> trace_tlb_flush_self(int vcpu)
> trace_tlb_flush_async_schedule(int from, int to)
> trace_tlb_flush
On Tue, Apr 25, 2017 at 04:24:18PM +0100, Alex Bennée wrote:
>
> Daniel P. Berrange writes:
>
> > On Tue, Apr 25, 2017 at 03:51:17PM +0100, Peter Maydell wrote:
> >> Hi; a recent travis build failure made me notice that our .travis.yml
> >> config references a preseed tarball from here:
> >> htt
* Peter Maydell (peter.mayd...@linaro.org) wrote:
> On 25 April 2017 at 16:05, Peter Maydell wrote:
> > info jit
> > qemu: qemu_mutex_lock: Invalid argument
>
> Repro without the qtest machinery:
>
> $ lldb -- ./aarch64-softmmu/qemu-system-aarch64 -M n810 -s -S -monitor
> stdio -machine
Since 2.7 commit (b2a575a Add optionrom compatible with fw_cfg DMA version)
regressed migration during firmware exection time by
abusing fwcfg.dma_enabled property to decide loading
dma version of option rom AND by mistake disabling DMA
for 2.6 and earlier globally instead of only for option rom.
Previously posted:
v1: https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg00201.html
v2: https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg05147.html
v3: https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg05671.html
v4: https://lists.gnu.org/archive/html/qemu-devel/2017-02/m
The block/crypto.c defines a set of QemuOpts that provide
parameters for encryption. This will also be needed by
the qcow/qcow2 integration, so expose the relevant pieces
in a new block/crypto.h header. Some helper methods taking
QemuOpts are changed to take QDict to simplify usage in
other places.
When integrating the crypto support with qcow/qcow2, we don't
want to use the bare LUKS option names "hash-alg", "key-secret",
etc. We want to namespace them "luks-hash-alg", "luks-key-secret"
so that they don't clash with any general qcow options at a later
date.
Reviewed-by: Max Reitz
Reviewed-
This converts the qcow2 driver to make use of the QCryptoBlock
APIs for encrypting image content, using the legacyy QCow2 AES
scheme.
With this change it is now required to use the QCryptoSecret
object for providing passwords, instead of the current block
password APIs / interactive prompting.
Document that use of guest virtual sector numbers as the basis for
the initialization vectors is a potential weakness, when combined
with internal snapshots or multiple images using the same passphrase.
This fixes the formatting of the itemized list too.
Reviewed-by: Max Reitz
Reviewed-by: Albert
The qcow driver refuses to open images which are less than
2 bytes in size, but will happily create such images. Add
a check in the create path to avoid this discrepancy.
Reviewed-by: Max Reitz
Reviewed-by: Alberto Garcia
Reviewed-by: Eric Blake
Signed-off-by: Daniel P. Berrange
---
block/qco
Test 042 is designed to verify operation with zero sized images.
Such images are not supported with qcow (v1), so this test has
always failed.
Reviewed-by: Max Reitz
Reviewed-by: Alberto Garcia
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/042 | 2 +-
1 file changed, 1 insertion(+),
Now that all encryption keys must be provided upfront via
the QCryptoSecret API and associated block driver properties
there is no need for any explicit encryption handling APIs
in the block layer. Encryption can be handled transparently
within the block driver. We only retain an API for querying
w
Instead of requiring separate input/output buffers for
encrypting data, change encrypt_sectors() to assume
use of a single buffer, encrypting in place. One current
caller uses the same buffer for input/output already
and the other two callers are easily converted to do so.
Reviewed-by: Alberto Gar
Historically the qcow & qcow2 image formats supported a property
"encryption=on" to enable their built-in AES encryption. We'll
soon be supporting LUKS for qcow2, so need a more general purpose
way to enable encryption, with a choice of formats.
This introduces an "encrypt.format" option, which wi
Test 048 is designed to verify data preservation during an
image resize. The qcow (v1) format impl has never supported
resize so always fails.
Reviewed-by: Max Reitz
Reviewed-by: Alberto Garcia
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/048 | 2 +-
1 file changed, 1 insertion(+),
This extends the 087 iotest to cover LUKS encryption when doing
blockdev-add.
Two further tests are added to validate read/write of LUKS
encrypted images with a single file and with a backing file.
Reviewed-by: Alberto Garcia
Reviewed-by: Max Reitz
Signed-off-by: Daniel P. Berrange
---
tests/
The 138 and 158 iotests exercise the legacy qcow2 aes encryption
code path and they work fine with qcow v1 too.
Reviewed-by: Alberto Garcia
Reviewed-by: Max Reitz
Signed-off-by: Daniel P. Berrange
---
tests/qemu-iotests/134 | 2 +-
tests/qemu-iotests/158 | 2 +-
2 files changed, 2 insertions(+
This converts the qcow driver to make use of the QCryptoBlock
APIs for encrypting image content. This is only wired up to
permit use of the legacy QCow encryption format. Users who wish
to have the strong LUKS format should switch to qcow2 instead.
With this change it is now required to use the QC
This adds support for using LUKS as an encryption format
with the qcow2 file, using the new encrypt.format parameter
to request "luks" format. e.g.
# qemu-img create --object secret,data=123456,id=sec0 \
-f qcow2 -o encrypt.-format=luks,encrypt.key-secret=sec0 \
test.qcow2 10G
The
Update the qcow2 specification to describe how the LUKS header is
placed inside a qcow2 file, when using LUKS encryption for the
qcow2 payload instead of the legacy AES-CBC encryption
Reviewed-by: Alberto Garcia
Reviewed-by: Max Reitz
Signed-off-by: Daniel P. Berrange
---
docs/specs/qcow2.txt
Now that qcow & qcow2 are wired up to get encryption keys
via the QCryptoSecret object, nothing is relying on the
interactive prompting for passwords. All the code related
to password prompting can thus be ripped out.
Reviewed-by: Alberto Garcia
Reviewed-by: Max Reitz
Signed-off-by: Daniel P. Be
Instead of requiring separate input/output buffers for
encrypting data, change qcow2_encrypt_sectors() to assume
use of a single buffer, encrypting in place. The current
callers all used the same buffer for input/output already.
Reviewed-by: Eric Blake
Reviewed-by: Fam Zheng
Reviewed-by: Alberto
While the crypto layer uses a fixed option name "key-secret",
the upper block layer may have a prefix on the options. e.g.
"luks-key-secret", "aes-key-secret", in order to avoid clashes
between crypto option names & other block option names. To
ensure the crypto layer can report accurate error mess
> On 25 Apr 2017, at 16:06 PM, P J P wrote:
>
> Vmware Paravirtual SCSI emulation uses command descriptors to
> process SCSI commands. These come with their message ring buffers.
> A guest could set the message ring page count to an arbitrary value
> resulting in infinite loop. Add check to avoi
Daniel P. Berrange writes:
> On Tue, Apr 25, 2017 at 04:24:18PM +0100, Alex Bennée wrote:
>>
>> Daniel P. Berrange writes:
>>
>> > On Tue, Apr 25, 2017 at 03:51:17PM +0100, Peter Maydell wrote:
>> >> Hi; a recent travis build failure made me notice that our .travis.yml
>> >> config references a
On Tue, Apr 25, 2017 at 11:13:17PM +0800, Fam Zheng wrote:
> Hi Kevin,
>
> This happens both on master and on your block-next tree:
>
> $ qemu-io -f raw null-co:// -c 'reopen -r'
> Unexpected error in bdrv_check_perm() at /stor/work/qemu/block.c:1437:
> Block node is read-only
> A
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Message-id: 20170425153858.25660-1-berra...@redhat.com
Subject: [Qemu-devel] [PATCH v6 00/18]Convert QCow[2] to QCryptoBlock & add
LUKS support
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script wil
On 04/25/2017 12:55 PM, Peter Lieven wrote:
Am 24.04.2017 um 22:13 schrieb Anton Nefedov:
On 24/04/2017 21:16, Peter Lieven wrote:
Am 24.04.2017 um 18:27 schrieb Anton Nefedov
:
On 04/21/2017 03:37 PM, Peter Lieven wrote:
Am 21.04.2017 um 14:19 schrieb Anton Nefedov:
On 04/21/2017 01:
*** This bug is a duplicate of bug 1463812 ***
https://bugs.launchpad.net/bugs/1463812
** This bug has been marked a duplicate of bug 1463812
qemu-system-ppc64 V2.30 cause RHEL5.9 disk corruption
--
You received this bug notification because you are a member of qemu-
devel-ml, which is su
On Apr 25, 2017 11:55 AM, "Alex Bennée" wrote:
Daniel P. Berrange writes:
> On Tue, Apr 25, 2017 at 04:24:18PM +0100, Alex Bennée wrote:
>>
>> Daniel P. Berrange writes:
>>
>> > On Tue, Apr 25, 2017 at 03:51:17PM +0100, Peter Maydell wrote:
>> >> Hi; a recent travis build failure made me noti
Ping?
Laurent
Le 01/03/2017 à 10:37, Laurent Vivier a écrit :
> This patch series byte-swap the uint64_t data stream
> of a file-descriptor opened with eventfd().
>
> It allows to pass more LTP test cases:
>
> eventfd011 TPASS : counter value matches required
> eventfd012 TPASS :
Ping?
Laurent
Le 02/03/2017 à 01:11, Laurent Vivier a écrit :
> On ppc, advice is arg2, not arg6:
>
> long ppc_fadvise64_64(int fd, int advice, u32 offset_high, u32 offset_low,
> u32 len_high, u32 len_low)
>
> Signed-off-by: Laurent Vivier
> ---
> linux-user/syscall.c |
Ping?
Laurent
Le 02/03/2017 à 01:54, Laurent Vivier a écrit :
> When a fd is opened using inotify_init(), a read provides
> one or more inotify_event structures:
>
> struct inotify_event {
> int wd;
> uint32_t mask;
> uint32_t cookie;
> uint32_t len;
>
Laurent Vivier wrote:
> On 25/04/2017 12:24, Juan Quintela wrote:
>> It only uses block/* functions, nothing from migration.
>>
>> Signed-off-by: Juan Quintela
>
> Reviewed-by: Laurent Vivier
>
> Perhaps the monitor.h include in savevm.c can be removed in PATCH 1/6?
hmp_info_snapshots still us
Laurent Vivier wrote:
> On 25/04/2017 12:24, Juan Quintela wrote:
>> This way we use the "normal" way of printing errors for hmp commands.
>>
>> --
>> Paolo suggestion
>
> "Suggested-by" tag?
Thanks.
>> {
>> +Error *err = NULL;
>> +
>> if (replay_snapshot) {
>> if (replay_mode
On Wed, Mar 22, 2017 at 02:32:39PM +0100, Igor Mammedov wrote:
> Signed-off-by: Igor Mammedov
> ---
> hw/arm/virt-acpi-build.c | 19 +++
> hw/arm/virt.c| 13 +++--
> 2 files changed, 14 insertions(+), 18 deletions(-)
>
> diff --git a/hw/arm/virt-acpi-build.c b
On 25/04/2017 19:00, Juan Quintela wrote:
> Laurent Vivier wrote:
>> On 25/04/2017 12:24, Juan Quintela wrote:
>>> This way we use the "normal" way of printing errors for hmp commands.
>>>
>>> --
>>> Paolo suggestion
>>
>> "Suggested-by" tag?
>
> Thanks.
>>> {
>>> +Error *err = NULL;
>>> +
>
On Wed, Mar 22, 2017 at 02:32:33PM +0100, Igor Mammedov wrote:
> it will allow switching from cpu_index to property based
> numa mapping in follow up patches.
>
> Signed-off-by: Igor Mammedov
> ---
> hw/arm/virt.c| 15 +++
> target/arm/cpu.c | 1 +
> 2 files changed, 16 insertio
On Tue, 25 Apr 2017, Markus Armbruster wrote:
> Stefano Stabellini writes:
>
> > On Mon, 24 Apr 2017, Peter Maydell wrote:
> >> On 24 April 2017 at 22:25, Stefano Stabellini
> >> wrote:
> >> > diff --git a/hw/9pfs/xen-9pfs.h b/hw/9pfs/xen-9pfs.h
> >> > new file mode 100644
> >> > index 000.
* Zhuangyanying (ann.zhuangyany...@huawei.com) wrote:
>
>
> > -Original Message-
> > From: Daniel P. Berrange [mailto:berra...@redhat.com]
> > Sent: Monday, April 24, 2017 6:34 PM
> > To: Dr. David Alan Gilbert
> > Cc: Zhuangyanying; Zhanghailiang; wangxin (U); qemu-devel@nongnu.org;
> >
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Message-id: 20170425153858.25660-1-berra...@redhat.com
Subject: [Qemu-devel] [PATCH v6 00/18]Convert QCow[2] to QCryptoBlock &
Hi Mark
Sorry for pinging so early.
Im just wondering if youve had time to go over my email below.
Any help would be greatly appreciated.
Thanks
Hoss
From: Qemu-devel on
behalf of Ajallooiean Hossein
Sent: Sunday, April 23, 2017 1:42:08 AM
To: qemu-de
Am 25.04.2017 um 15:42 schrieb Daniel P. Berrange:
On Mon, Apr 24, 2017 at 07:51:49PM +0200, Geert Martin Ijewski wrote:
+#ifdef _WIN32
+#include
+HCRYPTPROV hCryptProv;
+#else
+int fd; /* a file handle to either /dev/urandom or /dev/random */
+#endif
Lets mark both these vars 'static'
Ah
If no crypto library is included in the build, QEMU uses
qcrypto_random_bytes() to generate random data. That function tried to
open /dev/urandom or /dev/random and if openeing neither file worked it
errored out.
Those files obviously do not exist on windows, so there the code uses
CryptGenRan
Laurent Vivier wrote:
> On 25/04/2017 19:00, Juan Quintela wrote:
>> Laurent Vivier wrote:
>>> On 25/04/2017 12:24, Juan Quintela wrote:
{
+Error *err = NULL;
+
if (replay_snapshot) {
if (replay_mode == REPLAY_MODE_RECORD) {
-if (save_
Add emulation for Exynos4210 Pseudo Random Number Generator which could
work on fixed seeds or with seeds provided by True Random Number
Generator block inside the SoC.
Implement only the fixed seeds part of it in polling mode (no
interrupts).
Emulation tested with two independent Linux kernel ex
On 04/25/2017 03:18 PM, Thomas Huth wrote:
> qemu-system-s390x currently crashes when it is started with a
> virtio-scsi-pci device, e.g.:
>
> qemu-system-s390x -nographic -enable-kvm -device virtio-scsi-pci \
>-drive file=/tmp/disk.dat,if=none,id=d1,format=raw \
>
On 04/07/2017 10:30 AM, Amarnath Valluri wrote:
TPMDriverOps inside TPMBackend is not required, as it is supposed to be a class
member. The only possible reason for keeping in TPMBackend was, to get the
backend type in tpm.c where dedicated backend api, tpm_backend_get_type() is
present.
Signed-
On 04/07/2017 10:30 AM, Amarnath Valluri wrote:
Move thread handling inside TPMBackend, this way backend implementations need
not to maintain their own thread life cycle, instead they needs to implement
'handle_request()' class method that always been called from a thread.
This change made tpm_b
On 04/07/2017 10:30 AM, Amarnath Valluri wrote:
Initialize and free TPMBackend data members in it's own instance_init() and
instance_finalize methods.
Took the opportunity to fix object cleanup in tpm_backend_{create,destroy}
methods
Signed-off-by: Amarnath Valluri
---
backends/tpm.c
On 04/07/2017 10:30 AM, Amarnath Valluri wrote:
This allows backend implementations left optional interface methods.
For mandatory methods assertion checks added.
Signed-off-by: Amarnath Valluri
---
backends/tpm.c | 28 +---
hw/tpm/tpm_passthrough.c | 16 ---
Added a fix for the clang build, see
alpine.DEB.2.10.1704251014320.2875@sstabellini-ThinkPad-X260
The following changes since commit 55a19ad8b2d0797e3a8fe90ab99a9bb713824059:
Update version for v2.9.0-rc1 release (2017-03-21 17:13:29 +)
are available in the git repository at:
git://xen
From: Paul Durrant
This patch is a purely cosmetic change that avoids a name collision in
a subsequent patch.
Signed-off-by: Paul Durrant
Reviewed-by: Anthony Perard
Reviewed-by: Stefano Stabellini
---
include/exec/ram_addr.h | 4 ++--
include/hw/xen/xen.h| 2 +-
xen-hvm-stub.c
From: Juergen Gross
Today qemu is using e.g. the value 480 for Xen version 4.8.0. As some
Xen version tests are using ">" relations this scheme will lead to
problems when Xen version 4.10.0 is being reached.
Instead of the 3 digit schem use a 5 digit scheme (e.g. 40800 for
version 4.8.0).
Signe
From: Paul Durrant
This patch creates inline wrapper functions in xen_common.h for all open
coded calls to xc_hvm_XXX() functions outside of xen_common.h so that use
of xen_xc can be made implicit. This again is in preparation for the move
to using libxendevicemodel.
Signed-off-by: Paul Durrant
From: Paul Durrant
Doing this will make the transition to using the new libxendevicemodel
interface less intrusive on the callers of these functions, since using
the new library will require a change of handle.
NOTE: The patch also moves the 'externs' for xen_xc and xen_fmem from
xen_backe
From: Paul Durrant
This patch adds code in configure to set CONFIG_XEN_CTRL_INTERFACE_VERSION
to a new value of 490 if libxendevicemodel is present in the build
environment.
Signed-off-by: Paul Durrant
Signed-off-by: Stefano Stabellini
Reviewed-by: Anthony Perard
Reviewed-by: Stefano Stabelli
Introduce the Xen 9pfs backend: add struct XenDevOps to register as a
Xen backend and add struct V9fsTransport to register as v9fs transport.
All functions are empty stubs for now.
Signed-off-by: Stefano Stabellini
Reviewed-by: Greg Kurz
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: Ane
Upon receiving an event channel notification from the frontend, schedule
the bottom half. From the bottom half, read one request from the ring,
create a pdu and call pdu_submit to handle it.
For now, only handle one request per ring at a time.
Signed-off-by: Stefano Stabellini
CC: anthony.per...
From: Paul Durrant
This patch modifies the wrapper functions in xen_common.h to use the
new xendevicemodel interface if it is available along with compatibility
code to use the old libxenctrl interface if it is not.
Signed-off-by: Paul Durrant
Signed-off-by: Stefano Stabellini
Reviewed-by: Ant
From: Juergen Gross
Instead of trying to guess the Xen version to use by compiling various
test programs first just ask the system via pkg-config. Only if it
can't return the version fall back to the test program scheme.
If configure is being called with dedicated flags for the Xen libraries
use
Signed-off-by: Stefano Stabellini
Signed-off-by: Stefano Stabellini
Reviewed-by: Greg Kurz
CC: gr...@kaod.org
CC: anthony.per...@citrix.com
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 779c429..420505e 100644
--- a/MAINTAINERS
+++ b/MAINTAI
Implement xen_9pfs_init_in/out_iov_from_pdu and
xen_9pfs_pdu_vmarshal/vunmarshall by creating new sg pointing to the
data on the ring.
This is safe as we only handle one request per ring at any given time.
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: An
From: Paul Durrant
This patch adds a command-line option (-xen-domid-restrict) which will
use the new libxendevicemodel API to restrict devicemodel [1] operations
to the specified domid. (Such operations are not applicable to the xenpv
machine type).
This patch also adds a tracepoint to allow su
Write the limits of the backend to xenstore. Connect to the frontend.
Upon connection, allocate the rings according to the protocol
specification.
Initialize a QEMUBH to schedule work upon receiving an event channel
notification from the frontend.
Signed-off-by: Stefano Stabellini
CC: anthony.pe
Signed-off-by: Stefano Stabellini
Reviewed-by: Greg Kurz
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: Aneesh Kumar K.V
CC: Greg Kurz
---
hw/9pfs/Makefile.objs| 1 +
hw/xen/xen_backend.c | 3 +++
include/hw/xen/xen_backend.h | 3 +++
3 files changed, 7 insertions(+)
di
Public bug reported:
OS: Void Linux x86_64 (glibc)
QEMU version: 2.9.0
GDB version: 7.12.1
Problem description:
After I updated QEMU from version 2.8.1 to 2.9.0, I found that when I try to
connect GDB to a running QEMU and try to debug Real mode machine code, I can no
longer set architecture t
From: Paul Durrant
Commit f0f272baf3a7 "xen: use libxendevice model to restrict operations"
added a command-line option (-xen-domid-restrict) to limit operations
using the libxendevicemodel API to a specified domid. The commit also
noted that the restriction would be extended to cover operations
From: Anthony Xu
move xen-common.c to hw/xen/
Signed-off -by: Anthony Xu
Reviewed-by: Stefano Stabellini
---
Makefile.target | 2 -
hw/xen/Makefile.objs | 2 +-
hw/xen/xen-common.c | 169 +++
stubs/Makefile.objs | 1 +
stubs/xen-com
Use the new type in virtio-9p-device.
Signed-off-by: Stefano Stabellini
Reviewed-by: Greg Kurz
Reviewed-by: Philippe Mathieu-Daudé
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: Aneesh Kumar K.V
CC: Greg Kurz
---
hw/9pfs/9p.h | 6 ++
hw/9pfs/virtio-9p-device.c | 6 +-
From: Anthony Xu
move xen-mapcache.c to hw/i386/xen/
Signed-off -by: Anthony Xu
Reviewed-by: Stefano Stabellini
---
Makefile.target| 3 -
default-configs/i386-softmmu.mak | 1 -
default-configs/x86_64-softmmu.mak | 1 -
hw/i386/xen/Makefile.objs | 2 +-
Do not use the ring.h header installed on the system. Instead, import
the header into the QEMU codebase. This avoids problems when QEMU is
built against a Xen version too old to provide all the ring macros.
Signed-off-by: Stefano Stabellini
Reviewed-by: Greg Kurz
CC: anthony.per...@citrix.com
CC
Once a request is completed, xen_9pfs_push_and_notify gets called. In
xen_9pfs_push_and_notify, update the indexes (data has already been
copied to the sg by the common code) and send a notification to the
frontend.
Schedule the bottom-half to check if we already have any other requests
pending.
From: Anthony Xu
move xen-hvm.c to hw/i386/xen/
Signed-off -by: Anthony Xu
Reviewed-by: Stefano Stabellini
---
Makefile.target |3 +-
hw/i386/xen/Makefile.objs |2 +-
hw/i386/xen/trace-events | 11 +
hw/i386/xen/xen-hvm.c | 1429 +++
On 04/07/2017 10:30 AM, Amarnath Valluri wrote:
TPM configuration options are backend implementation details and shall not be
part of base TPMBackend object, and these shall not be accessed directly outside
of the class, hence added a new interface method, get_tpm_options() to
TPMDriverOps., whic
On Tue, Apr 25, 2017 at 07:28:07PM +0200, Geert Martin Ijewski wrote:
> If no crypto library is included in the build, QEMU uses
> qcrypto_random_bytes() to generate random data. That function tried to open
> /dev/urandom or /dev/random and if openeing neither file worked it errored
> out.
>
> Tho
On 04/07/2017 10:30 AM, Amarnath Valluri wrote:
As TPMBackend is a Qemu Object, we can use object_unref() inplace of
tpm_backend_destroy() to free the backend object, hence removed destroy() from
TPMDriverOps interface.
Signed-off-by: Amarnath Valluri
---
backends/tpm.c | 11 ---
On 04/25/2017 01:51 PM, Stefan Berger wrote:
>> +++ b/qapi-schema.json
>> @@ -5140,6 +5140,16 @@
>> { 'command': 'query-tpm-types', 'returns': ['TpmType'] }
>>
>> ##
>> +# @TPMOptions:
>> +#
>> +# Base type for TPM options
>> +#
>> +# Since: 2.10
>> +##
>> +{ 'struct': 'TPMOptions',
>> + 'dat
On 04/07/2017 10:30 AM, Amarnath Valluri wrote:
Provide base implementation of realloc_buffer(), so that backend implementations
can resue.
Signed-off-by: Amarnath Valluri
---
backends/tpm.c | 9 -
hw/tpm/tpm_passthrough.c | 12
2 files changed, 8 insertions(
On 04/25/2017 12:28 PM, Geert Martin Ijewski wrote:
> If no crypto library is included in the build, QEMU uses
> qcrypto_random_bytes() to generate random data. That function tried to
> open /dev/urandom or /dev/random and if openeing neither file worked it
s/openeing/opening/
s/opening neither fi
On 04/07/2017 10:30 AM, Amarnath Valluri wrote:
Signed-off-by: Amarnath Valluri
---
hw/tpm/tpm_passthrough.c | 64
hw/tpm/tpm_util.c| 25 +++
hw/tpm/tpm_util.h| 4 +++
3 files changed, 34 insertions(+), 59 del
On 24.04.2017 17:53, Eric Blake wrote:
> On 04/24/2017 10:47 AM, Eric Blake wrote:
>> On 04/24/2017 10:37 AM, Philippe Mathieu-Daudé wrote:
>>
> /*
> - * Returns true iff the first sector pointed to by 'buf' contains at
> least
> - * a non-NUL byte.
> + * Returns true if the fi
201 - 300 of 472 matches
Mail list logo
