On 04/29/2016 10:05 AM, Jason Wang wrote:
On 04/28/2016 06:25 PM, Zhang Chen wrote:
+static Packet *packet_new(CompareState *s, const void *data,
+ int size, ConnectionKey *key)
+{
+Packet *pkt = g_slice_new(Packet);
+
+pkt->data = g_memdup(data, size);
+
On Fri, 29 Apr 2016 15:32:22 +0800
Fam Zheng wrote:
> On Mon, 04/25 13:55, Dominik Dingel wrote:
> > While in the anonymous ram case we already take care of the right alignment
> > such an alignment gurantee does not exist for file backed ram allocation.
>
> s/gurantee/guarantee/
>
> Otherwise
On 29.04.2016 08:59, Bharata B Rao wrote:
> On Fri, Apr 29, 2016 at 08:45:37AM +0200, Thomas Huth wrote:
>> On 29.04.2016 05:24, David Gibson wrote:
>>> On Tue, Apr 26, 2016 at 04:03:37PM -0500, Michael Roth wrote:
>> ...
In the case of pseries, the DIMM abstraction isn't really exposed to
>>>
On Fri, Apr 29, 2016 at 9:09 AM, Jan Kiszka wrote:
> On 2016-04-25 00:12, David Kiarie wrote:
>> Add IVRS table for AMD IOMMU. Generate IVRS or DMAR
>> depending on emulated IOMMU
>
> It seems you lack scope descriptions for the PCI devices in the system.
> At least, this is what our jailhouse con
On 04/29/2016 10:07 AM, Jason Wang wrote:
On 04/28/2016 06:31 PM, Zhang Chen wrote:
+/*
+ * called from the compare thread on the primary
+ * for compare connection
+ */
+static void colo_compare_connection(void *opaque, void *user_data)
+{
+Connection *conn = opaque;
+Packet *pkt = N
Jan Vesely writes:
> On Tue, 2016-04-12 at 17:09 -0400, Jan Vesely wrote:
>> On Sat, 2016-03-19 at 21:18 -0400, Jan Vesely wrote:
>> >
>> > Fixes build with new linux headers.
>> >
>> > Signed-off-by: Jan Vesely
>> > ---
>> > linux-headers-4.5 and xfsprogs-3.2.4 in my case
>> >
>> > configur
On Fri, 29 Apr 2016 10:22:03 +0200
Thomas Huth wrote:
> On 29.04.2016 08:59, Bharata B Rao wrote:
> > On Fri, Apr 29, 2016 at 08:45:37AM +0200, Thomas Huth wrote:
> >> On 29.04.2016 05:24, David Gibson wrote:
> >>> On Tue, Apr 26, 2016 at 04:03:37PM -0500, Michael Roth wrote:
> >> ...
> >
Eric Blake writes:
> Our existing input visitors were not very consistent on errors
> in a function taking 'TYPE **obj' (that is, start_struct(),
> start_alternate(), type_str(), and type_any(). next_list() is
> similar, except that since commit 08f9541, it can't fail).
Multiple sentences in a p
On Thu, Apr 28, 2016 at 10:23:37PM -0600, Eric Blake wrote:
> Rather than rolling our own clone via an expensive conversion
> in and back out of QObject, use the generated QAPI version.
>
> Signed-off-by: Eric Blake
>
> ---
> v3: new patch
> ---
> util/qemu-sockets.c | 22 +-
On Thu, Apr 28, 2016 at 11:33:41PM +0200, Stefan Weil wrote:
> The clang compiler supports a useful compiler option -Weverything.
>
> As this option triggers warnings in glib header files, too, testing
> glib with -Werror will always fail. A size mismatch is also detected
> without -Werror, so sim
In the subject line, s/adjuest/adjust/ and s/requiement/requirement/.
On Wed, 04/20 11:34, Gonglei wrote:
> qemu_ram_unset_idstr() don't need rcu lock anymore,
s/don't/doesn't/
> meanwhile adjuest the range of rcu lock in
s/adjuest/adjust/ or just s/adjuest/make/
> qemu_ram_set_idstr() as smal
On Thu, 04/21 12:29, Janne Karhunen wrote:
> From: Janne Karhunen
>
> Vmdk images have metadata to indicate the vmware virtual
> hardware version image was created/tested to run with.
> Allow users to specify that version via new 'hwversion'
> option.
>
> Signed-off-by: Janne Karhunen
Sorry fo
On 29.04.2016 05:24, David Gibson wrote:
> On Tue, Apr 26, 2016 at 04:03:37PM -0500, Michael Roth wrote:
...
>> In the case of pseries, the DIMM abstraction isn't really exposed to
>> the guest, but rather the memory blocks we use to make the backing
>> memdev memory available to the guest. During
On Fri, 29 Apr 2016 13:28:50 +1000
David Gibson wrote:
> On Wed, Apr 27, 2016 at 03:37:05PM +0200, Igor Mammedov wrote:
> > On Tue, 26 Apr 2016 16:03:37 -0500
> > Michael Roth wrote:
> >
> > > Quoting Igor Mammedov (2016-04-26 02:52:36)
> > > > On Tue, 26 Apr 2016 10:39:23 +0530
> > > > Bha
On Wed, 04/20 11:34, Gonglei wrote:
> In this way, we can avoid to invoke qemu_get_ram_block()
> at most time, which can save cpu cycle.
>
> Signed-off-by: Gonglei
> ---
> exec.c | 48 ++--
> hw/misc/ivshmem.c | 6 --
> hw/v
On Wed, 04/20 11:34, Gonglei wrote:
> On the one hand, we have already qemu_get_ram_block() whose function
> is similar. On the other hand, we can directly use mr->ram_block but
> searching RAMblock by ram_addr which is a kind of waste.
>
> Signed-off-by: Gonglei
> ---
> exec.c
On Mon, 04/25 13:55, Dominik Dingel wrote:
> While in the anonymous ram case we already take care of the right alignment
> such an alignment gurantee does not exist for file backed ram allocation.
s/gurantee/guarantee/
Otherwise looks good to me,
Reviewed-by: Fam Zheng
>
> Instead, pagesize i
On 29.04.2016 06:08, Fam Zheng wrote:
On Thu, 04/28 15:16, Kevin Wolf wrote:
+typedef struct VmdkWriteCompressedCo {
+BlockDriverState *bs;
+int64_t sector_num;
+const uint8_t *buf;
+int nb_sectors;
+int ret;
+} VmdkWriteCompressedCo;
+
+static void vmdk_co_write_compressed(v
Eric Blake writes:
> In the QMP input visitor, visiting a list traverses two objects:
> the QAPI GenericList of the caller (which gets advanced in
> visit_next_list() regardless of this patch), and the QList input
> that we are converting to QAPI. For consistency with QDict
> visits, we want to
On 28 April 2016 at 22:33, Stefan Weil wrote:
> The clang compiler supports a useful compiler option -Weverything.
>
> As this option triggers warnings in glib header files, too, testing
> glib with -Werror will always fail. A size mismatch is also detected
> without -Werror, so simply remove it.
Hi,
> >
> > @@ -1447,8 +1432,9 @@ void qemu_ram_set_idstr(ram_addr_t addr, const
> char *name, DeviceState *dev)
> > }
> > pstrcat(new_block->idstr, sizeof(new_block->idstr), name);
> >
> > -QLIST_FOREACH_RCU(block, &ram_list.blocks, next) {
> > -if (block != new_block && !st
Am 29.04.2016 um 05:08 hat Fam Zheng geschrieben:
> On Thu, 04/28 15:16, Kevin Wolf wrote:
> > +typedef struct VmdkWriteCompressedCo {
> > +BlockDriverState *bs;
> > +int64_t sector_num;
> > +const uint8_t *buf;
> > +int nb_sectors;
> > +int ret;
> > +} VmdkWriteCompressedCo;
>
Stefan Weil writes:
> A compilation test with clang -Weverything reported this problem:
>
> config-host.h:112:20: warning: '$' in identifier
> [-Wdollar-in-identifier-extension]
>
> The line of code looks like this:
>
> #define CONFIG_TPM $(CONFIG_SOFTMMU)
>
> This is fine for Makefile code, but
> From: Fam Zheng [mailto:f...@redhat.com]
> Sent: Friday, April 29, 2016 3:57 PM
> To: Gonglei (Arei)
> Cc: qemu-devel@nongnu.org; pbonz...@redhat.com; Huangpeng (Peter)
> Subject: Re: [PATCH 2/3] exec: adjuest rcu_read_lock requiement
>
> In the subject line, s/adjuest/adjust/ and s/requiement/r
Eric Blake writes:
> Make sure the error message for visit_type_uint64() gracefully
> handles a NULL 'name' when called from the top level or a list
> context, as not all the world behaves like glibc in allowing
> NULL through a printf-family %s.
>
> Signed-off-by: Eric Blake
>
> ---
> v16: spli
> From: Fam Zheng [mailto:f...@redhat.com]
> Sent: Friday, April 29, 2016 4:07 PM
> To: Gonglei (Arei)
> Cc: qemu-devel@nongnu.org; pbonz...@redhat.com; Huangpeng (Peter)
> Subject: Re: [PATCH 3/3] memory: pass RAMBlock as a agrument
>
> On Wed, 04/20 11:34, Gonglei wrote:
> > In this way, we can
On Thu, Apr 28, 2016 at 01:36:05PM +0200, Kevin Wolf wrote:
> Commit d5941dd made the volume name configurable, but it didn't consider
> that the rw code compares the volume name string to assert that the
> first directory entry is the volume name. This made vvfat crash in rw
> mode.
>
> This fixe
On Thu, Apr 28, 2016 at 01:36:06PM +0200, Kevin Wolf wrote:
> Commit d5941dd documented that it leaves the default volume name as it
> was ("QEMU VVFAT"), but it doesn't actually implement this. You get an
> empty name (eleven space characters) instead.
>
> This fixes the implementation to apply t
On Thu, Apr 28, 2016 at 05:44:21PM -, Tom Yan wrote:
CCing Keith Busch , maintainer of QEMU NVMe.
Maybe he has an idea.
> Public bug reported:
>
> Full command: qemu-system-x86_64 -enable-kvm -cpu host -smp cores=4 -m
> 4G -net bridge -net nic -full-screen -drive
> file=ovmf_x64.bin,format=r
On Fri, Apr 29, 2016 at 08:45:37AM +0200, Thomas Huth wrote:
> On 29.04.2016 05:24, David Gibson wrote:
> > On Tue, Apr 26, 2016 at 04:03:37PM -0500, Michael Roth wrote:
> ...
> >> In the case of pseries, the DIMM abstraction isn't really exposed to
> >> the guest, but rather the memory blocks we u
Code changes look fine to me.
>
> Usually, Random Number Generator is abbreviated to RNG/rng.
> so replacing RndRandom with RngRandom seems more reasonable
> and keep consistent with RngBackend.
Reviewed-by: Pankaj Gupta
>
> Signed-off-by: Wei Jiangang
> ---
> backends/rng-random.c
hi, i want to implement the function of qcow2 resize which has snapshots.
each snapshot of qcow2 will have a separate total size, and when apply a
snapshot,
the image can be shrunk, and the total size of image will change after apply to
a snapshot
with different size.
now, there is a disk_si
Potential crash bug. Missing 2.6 wouldn't be a big deal, but it's an
obvious one-liner, so let's try.
The following changes since commit 736f85d5db701cc9d464a03b583d4a04606a0dd5:
Merge remote-tracking branch 'remotes/armbru/tags/pull-error-2016-04-28' into
staging (2016-04-28 11:05:37 +0100)
From: Eric Blake
Make sure the error message for visit_type_uint64() gracefully
handles a NULL 'name' when called from the top level or a list
context, as not all the world behaves like glibc in allowing
NULL through a printf-family %s.
Signed-off-by: Eric Blake
Message-Id: <1461879932-9020-21-
Am 29.04.2016 um 10:51 schrieb Peter Maydell:
> On 28 April 2016 at 22:33, Stefan Weil wrote:
>> The clang compiler supports a useful compiler option -Weverything.
>>
>> As this option triggers warnings in glib header files, too, testing
>> glib with -Werror will always fail. A size mismatch is al
Commit d5941dd made the volume name configurable, but it didn't consider
that the rw code compares the volume name string to assert that the
first directory entry is the volume name. This made vvfat crash in rw
mode.
This fixes the assertion to compare with the configured volume name
instead of a
Am 28.04.2016 um 15:16 hat Kevin Wolf geschrieben:
> This series introduces a new BlockDriver interface, which will hopefully be
> the
> final one, or at least good enough for another few years:
> .bdrv_preadv/pwritev.
> It is based on coroutines, vectored, has flags and uses a byte granularity.
The following changes since commit 0d48dfedc5c2beb418ad4c08b78de14e794bb199:
slirp: fix guest network access with darwin host (2016-04-28 18:12:08 +0100)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
for you to fetch changes up to d208c50d9dbf98c0
Am 22.04.2016 um 19:42 hat Kevin Wolf geschrieben:
> This is another feature that was "logically" part of the BlockBackend, but
> implemented as a BlockDriverState feature. It was always kept on top using
> swap_feature_fields().
>
> This series moves it to be actually implemented in the BlockBack
Commit d5941dd documented that it leaves the default volume name as it
was ("QEMU VVFAT"), but it doesn't actually implement this. You get an
empty name (eleven space characters) instead.
This fixes the implementation to apply the advertised default.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Kevi
Am 29.04.2016 um 10:49 hat Pavel Butsykin geschrieben:
> On 29.04.2016 06:08, Fam Zheng wrote:
> >On Thu, 04/28 15:16, Kevin Wolf wrote:
> >> static int vmdk_write_compressed(BlockDriverState *bs,
> >> int64_t sector_num,
> >> con
On 4/13/2016 5:06 PM, Michael S. Tsirkin wrote:
> On Wed, Apr 13, 2016 at 12:15:38PM +0100, Dr. David Alan Gilbert wrote:
>> * Michael S. Tsirkin (m...@redhat.com) wrote:
>>> On Wed, Apr 13, 2016 at 04:24:55PM +0530, Jitendra Kolhe wrote:
Can we extend support for post-copy in a different patc
Hi
On Thu, Apr 28, 2016 at 7:23 AM, Yuanhan Liu
wrote:
> On Fri, Apr 01, 2016 at 01:16:21PM +0200, marcandre.lur...@redhat.com wrote:
>> From: Marc-André Lureau
>>
>> Signed-off-by: Marc-André Lureau
>> ---
>> docs/specs/vhost-user.txt | 15 +++
>> hw/virtio/vhost-user.c| 16 ++
On 29.04.2016 12:49, Kevin Wolf wrote:
Am 29.04.2016 um 10:49 hat Pavel Butsykin geschrieben:
On 29.04.2016 06:08, Fam Zheng wrote:
On Thu, 04/28 15:16, Kevin Wolf wrote:
static int vmdk_write_compressed(BlockDriverState *bs,
int64_t sector_num,
On Fri, Apr 29, 2016 at 08:45:37AM +0200, Thomas Huth wrote:
> On 29.04.2016 05:24, David Gibson wrote:
> > On Tue, Apr 26, 2016 at 04:03:37PM -0500, Michael Roth wrote:
> ...
> >> In the case of pseries, the DIMM abstraction isn't really exposed to
> >> the guest, but rather the memory blocks we u
Please use my kernel.org email address. Also CC relevant maintainers.
On Fri, 29 Apr 2016, Chunyan Liu wrote:
> Since commit a1666142: acpi-build: make ROMs RAM blocks resizeable,
> xen HVM direct kernel boot failed. Xen HVM direct kernel boot will
> insert a linuxboot.bin or multiboot.bin to /gen
On 29.04.2016 10:30, Igor Mammedov wrote:
> On Fri, 29 Apr 2016 10:22:03 +0200
> Thomas Huth wrote:
>
>> On 29.04.2016 08:59, Bharata B Rao wrote:
>>> On Fri, Apr 29, 2016 at 08:45:37AM +0200, Thomas Huth wrote:
On 29.04.2016 05:24, David Gibson wrote:
> On Tue, Apr 26, 2016 at 04:03
Hi Markus,
sorry for replying so late, I am stucked by other tasks for a while.
On 04/12/2016 07:50 PM, Markus Armbruster wrote:
Examine how it uses msi_init(). That's how we give a PCI device
capability MSI. If the device model treats msi_init() failure as fatal,
it doesn't have a non-MS
On 29 April 2016 at 10:19, Markus Armbruster wrote:
> Potential crash bug. Missing 2.6 wouldn't be a big deal, but it's an
> obvious one-liner, so let's try.
>
> The following changes since commit 736f85d5db701cc9d464a03b583d4a04606a0dd5:
>
> Merge remote-tracking branch 'remotes/armbru/tags/pu
Eric Blake writes:
> 2.7 material; much less churn this time through, but enough
> that it was easier for me to repost than to make Markus do
> the touchups his review found.
>
> Based on master, with no prerequisite patches.
>
> Also available as a tag at this location:
> git fetch git://repo.or
Yeah, thank you Alex.
If I use a linux on top of the qemu, for entering debug mode, do i need to
compile kernel from source or it is not dependent on debugging qemu itself?
and then is it possible to define a heterogeneous multicore platform in qemu?
Thanks and regards.
* Zhang Chen (zhangchen.f...@cn.fujitsu.com) wrote:
>
>
> On 04/29/2016 10:07 AM, Jason Wang wrote:
> >
> >On 04/28/2016 06:31 PM, Zhang Chen wrote:
> +/*
> + * called from the compare thread on the primary
> + * for compare connection
> + */
> +static void colo_compare_connec
* Eric Blake (ebl...@redhat.com) wrote:
> On 04/27/2016 01:08 PM, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert"
> >
> > On the source, add a count of page requests received from the
> > destination.
> >
> > Signed-off-by: Dr. David Alan Gilbert
> > ---
> > hmp.c
Eric Blake writes:
> 'qobject-json.h' is not a QObject subtype; include this file
> directly in .c files that are using it, rather than abusing
> qmp/types.h for that purpose.
>
> Meanwhile, for files that include a list of individual QObject
> subtypes, it's easier to just use qmp/types.h for th
On Thu, Feb 25, 2016 at 05:41:00PM +, Peter Maydell wrote:
> On 19 February 2016 at 20:04, Edgar E. Iglesias
> wrote:
> > From: "Edgar E. Iglesias"
> >
> > Add the following flags to the data abort syndrome generator:
> > * isv - Instruction syndrome valid
> > * sas - Syndrome access size
> >
On Fri 29 Apr 2016 12:01:08 PM CEST, Kevin Wolf wrote:
>> This is another feature that was "logically" part of the
>> BlockBackend, but implemented as a BlockDriverState feature. It was
>> always kept on top using swap_feature_fields().
>>
>> This series moves it to be actually implemented in the
On Thu, Feb 25, 2016 at 06:26:45PM +, Peter Maydell wrote:
> On 19 February 2016 at 20:04, Edgar E. Iglesias
> wrote:
> > From: "Edgar E. Iglesias"
> >
> > Add support for generating the instruction syndrome for Data Aborts.
> > These syndromes are used by hypervisors for example to trap and
On 29 April 2016 at 10:55, Kevin Wolf wrote:
> The following changes since commit 0d48dfedc5c2beb418ad4c08b78de14e794bb199:
>
> slirp: fix guest network access with darwin host (2016-04-28 18:12:08 +0100)
>
> are available in the git repository at:
>
> git://repo.or.cz/qemu/kevin.git tags/for-
From: "Edgar E. Iglesias"
Use tcg_set_insn_param() instead of directly accessing internal
tcg data structures to update an insn param.
Reviewed-by: Richard Henderson
Signed-off-by: Edgar E. Iglesias
---
include/exec/gen-icount.h | 16
1 file changed, 8 insertions(+), 8 deleti
From: "Edgar E. Iglesias"
Add tcg_set_insn_param as a mechanism to modify an insn
parameter after emiting the insn. This is useful for icount
and also for embedding fault information for a specific insn.
Reviewed-by: Richard Henderson
Signed-off-by: Edgar E. Iglesias
---
tcg/tcg.h | 6 ++
From: "Edgar E. Iglesias"
Hi,
Another round of patches towards EL2 support. This one adds partial
Instruction Syndrome generation for Data Aborts while running in AArch64.
I don't feel very confident with the way I collect the regsize info used
to fill out the SF field. Feedback on that would b
Eric Blake writes:
> Pull out a new qstring_append_json_string() helper, so that all
> JSON output producers can use the same output escaping rules.
>
> While it appears that vmstate's use of the simpler qjson.c
> formatter is not currently encountering any string that needs
> escapes to be valid
From: "Edgar E. Iglesias"
The various load/store variants under disas_ldst_reg can all reuse the
same decoding for opc, size, rt and is_vector.
This patch unifies the decoding in preparation for generating
instruction syndromes for data aborts.
This will allow us to reduce the number of places t
From: "Edgar E. Iglesias"
Split the data abort syndrome generator into two versions.
One with a valid Instruction Specific Syndrome (ISS) and another without.
The following new flags are supported by the syndrome generator
with ISS:
* isv - Instruction syndrome valid
* sas - Syndrome access size
From: "Edgar E. Iglesias"
Add support for generating the instruction syndrome for Data Aborts.
These syndromes are used by hypervisors for example to trap and emulate
memory accesses.
We save the decoded data out-of-band with the TBs at translation time.
When exceptions hit, the extra data attac
On 04/29/2016 02:28 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> Our existing input visitors were not very consistent on errors
>> in a function taking 'TYPE **obj' (that is, start_struct(),
>> start_alternate(), type_str(), and type_any(). next_list() is
>> similar, except that since c
On 04/29/2016 02:50 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> In the QMP input visitor, visiting a list traverses two objects:
>> the QAPI GenericList of the caller (which gets advanced in
>> visit_next_list() regardless of this patch), and the QList input
>> that we are converting t
On 04/29/2016 05:13 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> 2.7 material; much less churn this time through, but enough
>> that it was easier for me to repost than to make Markus do
>> the touchups his review found.
>>
>> Based on master, with no prerequisite patches.
>>
>> Also av
On 04/29/2016 06:10 AM, Eric Blake wrote:
> On 04/29/2016 02:28 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> Our existing input visitors were not very consistent on errors
>>> in a function taking 'TYPE **obj' (that is, start_struct(),
>>> start_alternate(), type_str(), and type_any()
tutu sky writes:
> Yeah, thank you Alex.
> If I use a linux on top of the qemu, for entering debug mode, do i
> need to compile kernel from source or it is not dependent on debugging
> qemu itself?
I'm not sure I follow. As far as QEMU is concerned it provides a stub
for GDB to talk to and does
Magic answer, Thanks a lot Alex.
you mean GDB will be enabled for just QEMU's itself internals? It does not make
importance or any difference for guest running on it?
if i want describe my opinion in another way, i think you said that when
enabling GDB for QEMU, it is usable and is just important
'make check' fails with:
ERROR:tests/bios-tables-test.c:493:load_expected_aml:
assertion failed: (g_file_test(aml_file, G_FILE_TEST_EXISTS))
since commit:
caf50c7166a6ed96c462ab5db4b495e1234e4cc6
tests: pc: acpi: drop not needed 'expected SSDT' blobs
Assert happens because qemu-system-x86_64
Cao jin writes:
> Hi Markus,
> sorry for replying so late, I am stucked by other tasks for a while.
>
> On 04/12/2016 07:50 PM, Markus Armbruster wrote:
>>
>> Examine how it uses msi_init(). That's how we give a PCI device
>> capability MSI. If the device model treats msi_init() failure as
Eric Blake writes:
> On 04/29/2016 06:10 AM, Eric Blake wrote:
>> On 04/29/2016 02:28 AM, Markus Armbruster wrote:
>>> Eric Blake writes:
>>>
Our existing input visitors were not very consistent on errors
in a function taking 'TYPE **obj' (that is, start_struct(),
start_alternate(
Eric Blake writes:
> On 04/29/2016 02:50 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> In the QMP input visitor, visiting a list traverses two objects:
>>> the QAPI GenericList of the caller (which gets advanced in
>>> visit_next_list() regardless of this patch), and the QList input
From: "Edgar E. Iglesias"
Use extract32 instead of open coding the bit masking when decoding
is_signed and is_extended. This streamlines the decoding with some
of the other ldst variants.
No functional change.
Reviewed-by: Sergey Fedorov
Signed-off-by: Edgar E. Iglesias
---
target-arm/transl
On Sun Apr 24 22:05:43 2016, liqiang...@360.cn wrote:
> Hi, Is there any progress in requesting CVE for this issue ?
>
> -邮件原件-
> 发件人: Michael S. Tsirkin [mailto:m...@redhat.com]
> 发送时间: 2016年4月18日 17:29
> 收件人: 李强
> 抄送: Peter Maydell; pmato...@redhat.com; sstabell...@kernel.org;
> secal...@
Fixes build failure with --enable-xfsctl and
new linux headers (>=4.5) and older xfsprogs(<4.5):
In file included from /usr/include/xfs/xfs.h:38:0,
from
/var/tmp/portage/app-emulation/qemu-2.5.0-r1/work/qemu-2.5.0/block/raw-posix.c:97:
/usr/include/xfs/xfs_fs.h:42:8: error: redefi
Eric Blake writes:
> On 04/29/2016 05:13 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> 2.7 material; much less churn this time through, but enough
>>> that it was easier for me to repost than to make Markus do
>>> the touchups his review found.
>>>
>>> Based on master, with no prere
On 29/04/2016 14:44, Igor Mammedov wrote:
> 'make check' fails with:
>
> ERROR:tests/bios-tables-test.c:493:load_expected_aml:
>assertion failed: (g_file_test(aml_file, G_FILE_TEST_EXISTS))
>
> since commit:
> caf50c7166a6ed96c462ab5db4b495e1234e4cc6
> tests: pc: acpi: drop not needed 'expe
From: "Edgar E. Iglesias"
Add the IL flag to syn_data_abort(). Since we at the moment
never set ISV, the IL flag is always set to one.
Signed-off-by: Edgar E. Iglesias
---
target-arm/internals.h | 4 +++-
target-arm/op_helper.c | 6 --
2 files changed, 7 insertions(+), 3 deletions(-)
diff
Eric Blake writes:
> Pull out a new qstring_append_json_number() helper, so that all
> JSON output producers can use a consistent style for printing
> floating point without duplicating code (since we are doing more
> data massaging than a simple printf format can handle).
>
> Address one FIXME b
Eric Blake writes:
> No need to create a temporary buffer, when we already have a
> function available for our needs.
>
> Signed-off-by: Eric Blake
> Reviewed-by: Fam Zheng
>
> ---
> v3: no change
> v2: no change
> ---
> qobject/json-parser.c | 7 +--
> 1 file changed, 1 insertion(+), 6 de
Hi Guangrong,
How about also add SGX to Skylake?
Thanks,
-Kai
On 4/27/2016 8:13 PM, Xiao Guangrong wrote:
From: Eduardo Habkost
Introduce Skylake-Client cpu mode which inherits the features from
Broadwell and supports some additional features that are: MPX,
XSAVEC, XSAVES and XGETBV1
Note:
The S390 virtual css support already has a mechanism to build virtual
schib and provide virtual subchannels to the guest. However, to
pass-through ccw device to a guest, we need to introduce a new
mechanism to build its schib according to the real device information.
Thus we realize a new css_sch_b
This is a placeholder for a linux-headers update.
Signed-off-by: Xiao Feng Ren
---
linux-headers/linux/vfio.h | 32
1 file changed, 32 insertions(+)
diff --git a/linux-headers/linux/vfio.h b/linux-headers/linux/vfio.h
index 759b850..4059e3e 100644
--- a/linux-he
Add qemu support for the newly introduced VFIO No-IOMMU driver.
We need to add special handling for:
- Group character device is /dev/vfio/noiommu-$GROUP.
- No-IOMMU does not rely on a memory listener.
- No IOMMU will be set for its group, so no need to call
vfio_kvm_device_add_group.
Signed-of
hi, i want to implement the function of qcow2 resize which has snapshots.
each snapshot of qcow2 will have a separate total size, and when apply a
snapshot,
the image can be shrunk, and the total size of image will change after apply to
a snapshot
with different size.
now, there is a disk_si
Implement a basic infrastructure of handling channel I/O instruction
interception for passed through devices:
1. Branch the code path of instruction interception handling by
SubChannel type.
2. For a passed through device, issue the ORB to do ccw translation
and perform an I/O operation.
3. I
The patch series introduce a basic channel I/O passthrough
infrastructure based on vfio.
- Focus on supporting dasd-eckd(cu_type/dev_type = 0x3990/0x3390) as
the target device.
- Support new qemu parameters in the style of:
"-machine s390-ccw-virtio(,s390-map-css=on|off) ...
-device vfio
We want to support real (i.e. not virtual) channel devices
even for guests that do not support MCSS-E (where guests may
see devices from any channel subsystem image at once). As all
virtio-ccw devices are in css 0xfe (and show up in the default
css 0 for guests not activating MCSS-E), we need an op
In order to support ccw device pass-through, we introduce a s390
ccw device called "s390-ccw" to hold the real device info. As the
existing virtual-css-bridge and virtual-css-bus are designed to
support virtio_ccw devices for S390x virtio machine. We want to put
passthroughed devices on a different
We use the No-IOMMU mode of VFIO to realize the ccw device
passthrough, implement a vfio based ccw passthrough
driver called "vfio-ccw".
Support qemu parameters in the style of:
"-device vfio-ccw,id=xx,hostid=xx(,guestid=xx)"
Signed-off-by: Xiao Feng Ren
---
default-configs/s390x-softmmu.mak |
Introduce CcwChain structures and helper functions that can be used
to translate a guest ccw program to a user-space ccw program.
The following limitations apply:
1. Support only prefetch enable mode.
2. Support chain for idal(c64) ccws.
3. Detect chain end only by CC and DC flags.
This work prepa
Introduce device information about vfio-ccw: VFIO_DEVICE_FLAGS_CCW.
Realize VFIO_DEVICE_GET_INFO ioctl for vfio-ccw.
Signed-off-by: Dong Jia Shi
Reviewed-by: Pierre Morel
---
drivers/vfio/ccw/vfio_ccw.c | 20
include/uapi/linux/vfio.h | 1 +
2 files changed, 21 insertion
Introduce ccwchain structure and helper functions that can be used to
handle special ccw programs issued from user-space.
The following limitations apply:
1. Supports only prefetch enabled mode.
2. Supports direct ccw chaining by translating them to idal ccws.
3. Supports idal(c64) ccw chaining.
Introduce a new callback on ccw device to handle ccw-request.
Realize the callback in vfio-ccw device.
Signed-off-by: Xiao Feng Ren
---
hw/s390x/s390-ccw.h | 1 +
hw/vfio/ccw.c | 42 ++
2 files changed, 43 insertions(+)
diff --git a/hw/s390x/s390-c
Let's make orb-related definitions available outside
of the common I/O layer for future use (e.g. for
passing channel devices to a guest).
Signed-off-by: Dong Jia Shi
Reviewed-by: Pierre Morel
---
{drivers/s390/cio => arch/s390/include/asm}/orb.h | 0
drivers/s390/cio/eadm_sch.c
This enables IOMMU API if CONFIG_CCW is configured.
Signed-off-by: Dong Jia Shi
Reviewed-by: Pierre Morel
---
drivers/iommu/Kconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
index dd1dc39..63bbc3d 100644
--- a/drivers
vfio: ccw: basic vfio-ccw infrastructure
Introduction
Here we describe the vfio support for Channel I/O devices (aka. CCW
devices) for Linux/s390. Motivation for vfio-ccw is to passthrough CCW
devices to a virtual machine, while vfio is the me
1 - 100 of 195 matches
Mail list logo
