On Thu, May 12, 2016 at 15:20:51 +0200, Igor Mammedov wrote:
> On Thu, 12 May 2016 13:04:23 +0200
> Peter Krempa wrote:
>
> > On Thu, May 12, 2016 at 07:52:23 -0300, Eduardo Habkost wrote:
> > > I don't think we should do that, unless users already had time to
> > > update
On Thu, 12 May 2016 13:04:23 +0200
Peter Krempa wrote:
> On Thu, May 12, 2016 at 07:52:23 -0300, Eduardo Habkost wrote:
> > I don't think we should do that, unless users already had time to
> > update their scripts and libvirt had time to implement code
> > supporting the new
On Fri, Jan 29, 2016 at 12:15:12PM -0200, Eduardo Habkost wrote:
> On Thu, Jan 28, 2016 at 07:01:12PM +0200, Michael S. Tsirkin wrote:
> > On Thu, Jan 28, 2016 at 01:02:26PM -0200, Eduardo Habkost wrote:
> > > If the same GlobalProperty struct is registered twice, the list
> > > entry gets
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1455475
Title:
Block
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1455475
Title:
Block Commit: [100 %]error: failed to pivot job for disk vda
On 12/05/2016 14:03, Eduardo Habkost wrote:
> > Item number 2 on the other hand means that it's okay to add Skylake CPU
> > models without XSAVES. Because of the large number of kernels in the
> > wild that block XSAVES, I'm inclined to do that.
>
> Agreed. Now, should we name the CPU model
On Mon, May 09, 2016 at 03:44:57PM +0200, Paolo Bonzini wrote:
[...]
> 2) KVM doesn't yet expose any XSAVES state save component, and the only
> one defined in Skylake (processor tracing) probably will block migration
> and will have to be added separately.
>
[...]
> Item number 2 on the other
On Mon, May 09, 2016 at 06:44:00PM +0200, Aurelien Jarno wrote:
> 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
On 11/05/2016 21:55, Lluís Vilanova wrote:
>
> diff --git a/translate-all.c b/translate-all.c
> index 8329ea6..1c16b14 100644
> --- a/translate-all.c
> +++ b/translate-all.c
> @@ -1092,6 +1092,8 @@ TranslationBlock *tb_gen_code(CPUState *cpu,
> ti = profile_getclock();
> #endif
>
> +
On 12/05/2016 13:25, Paolo Bonzini wrote:
>> > r->req.aiocb = dma_blk_read(s->qdev.conf.blk, r->req.sg,
>> > r->sector,
>> > scsi_dma_complete, r);
> This is broken, it should be changed to an offset in the previous patch.
>
> Please rename the
On 06/05/2016 18:26, Eric Blake wrote:
> @@ -340,11 +338,12 @@ static void scsi_do_read(SCSIDiskReq *r, int ret)
> r->req.aiocb = dma_blk_read(s->qdev.conf.blk, r->req.sg, r->sector,
> scsi_dma_complete, r);
This is broken, it should be changed to
On Thu, May 12, 2016 at 09:19:48AM +0200, Jiri Denemark wrote:
> On Wed, May 11, 2016 at 16:35:50 -0300, Eduardo Habkost wrote:
> > # @CpuDefinitionInfo:
> > #
> > # Virtual CPU definition.
> > #
> > # @name: the name of the CPU definition
> > # @runnable: #optional. whether the CPU model us
On Thu, May 12, 2016 at 07:52:23 -0300, Eduardo Habkost wrote:
> I don't think we should do that, unless users already had time to
> update their scripts and libvirt had time to implement code
> supporting the new method.
>
> I believe libvirt (and people's scripts) use maxcpus only when
> they
Hi Petros,
I'm sorry for the off-thread reply (I'm not subscribed at qemu-devel so please
CC me in your replies).
I believe that we should modify the envp array in order to include the
Qemu-related variables that a user might define:
>+return get_errno(execve(qemu_execve_path, new_argp,
On Thu, May 12, 2016 at 12:29:55PM +0200, Igor Mammedov wrote:
> On Thu, 12 May 2016 10:07:03 +0300
> "Michael S. Tsirkin" wrote:
>
> > On Wed, May 11, 2016 at 08:28:59PM -0300, Eduardo Habkost wrote:
> > > On Thu, May 12, 2016 at 12:51:55AM +0300, Michael S. Tsirkin wrote:
>
On Thu, 12 May 2016 10:05:54 +0300
"Michael S. Tsirkin" wrote:
> On Wed, May 11, 2016 at 08:36:00PM -0300, Eduardo Habkost wrote:
> > On Wed, May 11, 2016 at 03:50:39PM +0200, Igor Mammedov wrote:
> > > On Tue, 10 May 2016 17:24:14 -0300
> > > Eduardo Habkost
Am 12.05.2016 um 11:00 hat Denis V. Lunev geschrieben:
> On 05/11/2016 02:28 PM, Kevin Wolf wrote:
> >Am 11.05.2016 um 09:00 hat Denis V. Lunev geschrieben:
> >>There is a possibility that qcow2_co_write_zeroes() will be called
> >>with the partial block. This could be synthetically triggered with
On 05/11/2016 02:28 PM, Kevin Wolf wrote:
Am 11.05.2016 um 09:00 hat Denis V. Lunev geschrieben:
There is a possibility that qcow2_co_write_zeroes() will be called
with the partial block. This could be synthetically triggered with
qemu-io -c "write -z 32k 4k"
and can happen in the real
On Thu, 12 May 2016 11:09:02 +0100
Stefan Hajnoczi wrote:
> On Tue, May 10, 2016 at 01:55:10PM +0200, Petr Tesarik wrote:
> > On Tue, 10 May 2016 10:56:42 +0100
> > Stefan Hajnoczi wrote:
> >
> > > On Tue, May 10, 2016 at 07:59:41AM +0200, Petr Tesarik
On Thu, 12 May 2016 10:07:03 +0300
"Michael S. Tsirkin" wrote:
> On Wed, May 11, 2016 at 08:28:59PM -0300, Eduardo Habkost wrote:
> > On Thu, May 12, 2016 at 12:51:55AM +0300, Michael S. Tsirkin wrote:
> > > On Wed, May 11, 2016 at 03:50:39PM +0200, Igor Mammedov wrote:
> >
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
On Tue, May 10, 2016 at 01:55:10PM +0200, Petr Tesarik wrote:
> On Tue, 10 May 2016 10:56:42 +0100
> Stefan Hajnoczi wrote:
>
> > On Tue, May 10, 2016 at 07:59:41AM +0200, Petr Tesarik wrote:
> > > On Mon, 9 May 2016 09:52:28 -0600
> > > Eric Blake wrote:
For better performance, we can use RAMblock
directly stored in memory_region at present.
Signed-off-by: Gonglei
---
exec.c | 33 ++---
hw/misc/ivshmem.c | 8 +---
hw/virtio/vhost-user.c | 13 -
Please see the details in each patch.
v3 -> v2:
- rebase on the master
- resend because Delivery has failed to these recipients or groups:
qemu-devel@nongnu.org
v2 -> v1:
- rework an argument's name for clearity in patch 1. [Fam]
- fix some typos in patch 2. [Fam]
- touche block->fd
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
Reviewed-by: Fam Zheng
---
exec.c
Remove the unnecessary NULL check.
Signed-off-by: Gonglei
Reviewed-by: Paolo Bonzini
---
ui/spice-display.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/ui/spice-display.c b/ui/spice-display.c
index 242ab5f..1ffbec1 100644
CID 1352419, using g_strdup_printf instead of asprintf.
Signed-off-by: Gonglei
Reviewed-by: Paolo Bonzini
---
ui/egl-helpers.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/ui/egl-helpers.c b/ui/egl-helpers.c
index
Rebase on the latest master brunch.
Gonglei (2):
egl-helpers: fix possible resource leak
spice: fix coverity complains
ui/egl-helpers.c | 9 +++--
ui/spice-display.c | 4 +---
2 files changed, 4 insertions(+), 9 deletions(-)
--
1.7.12.4
Without presuming if we got there because of a user mistake or some
more subtile bug in the tooling, it doesn't hurt to log somewhere that
the device won't be functional.
Signed-off-by: Greg Kurz
---
hw/virtio/virtio-pci.c |4
1 file changed, 4 insertions(+)
On Tue, May 10, 2016 at 05:59:08PM +0800, Changlong Xie wrote:
> Signed-off-by: Changlong Xie
> ---
> util/rfifolock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, applied to my block tree:
https://github.com/stefanha/qemu/commits/block
Stefan
On Thu, May 12, 2016 at 02:39:50PM +0530, Ashi wrote:
> On Wednesday 04 May 2016 02:09 PM, Daniel P. Berrange wrote:
> > On Tue, May 03, 2016 at 11:43:58PM +0530, Ashi wrote:
> > >
> > >
> > > On Tuesday 03 May 2016 07:31 PM, Daniel P. Berrange wrote:
> > > > On Tue, May 03, 2016 at 07:04:17PM
On Wednesday 04 May 2016 02:09 PM, Daniel P. Berrange wrote:
On Tue, May 03, 2016 at 11:43:58PM +0530, Ashi wrote:
On Tuesday 03 May 2016 07:31 PM, Daniel P. Berrange wrote:
On Tue, May 03, 2016 at 07:04:17PM +0530, Ashijeet Acharya wrote:
From: Ashijeet
On 05/11/2016 04:57 PM, Cornelia Huck wrote:
> Hi,
>
> here's an update of the s390x patches I have queued for 2.7.
>
> Changes from v1:
> - Avoid the 'IplBlockCcw fcp;' error in patch 3 from the start
> instead of fixing it in a later patch (as noted by Christian)
> - Add Xiaoqiang Zhao's
On 05/12/2016 04:07 PM, Jason Wang wrote:
On 2016年05月12日 14:33, Zhang Chen wrote:
+ret = net_fill_rstate(>rs, buf, size);
+
+if (ret == -1) {
+goto eoc;
+} else if (ret == 1) {
+if (qemu_send_packet_async(>nc, s->rs.buf,
+
Hi, Kirti/Neo, any response for below comment?
> From: Tian, Kevin
> Sent: Wednesday, May 04, 2016 10:59 AM
>
> > From: Alex Williamson
> > Sent: Wednesday, May 04, 2016 6:44 AM
> > > +/**
> > > + * struct gpu_device_ops - Structure to be registered for each physical
> > > GPU to
> > > + *
On 2016年05月12日 14:33, Zhang Chen wrote:
+ret = net_fill_rstate(>rs, buf, size);
+
+if (ret == -1) {
+goto eoc;
+} else if (ret == 1) {
+if (qemu_send_packet_async(>nc, s->rs.buf,
+ s->rs.packet_len,
+ net_socket_send_completed) ==
On 05/12/2016 04:01 PM, Jason Wang wrote:
On 2016年05月12日 14:49, Zhang Chen wrote:
On 05/09/2016 06:49 PM, Zhang Chen wrote:
+
+s->chr_sec_in = qemu_chr_find(s->sec_indev);
+if (s->chr_sec_in == NULL) {
+error_setg(errp, "Secondary IN Device '%s' not found",
+
On Thu, 12 May 2016 09:40:21 +0200
Christian Borntraeger wrote:
> Maybe a topic for this years QEMU summit could be to talk about
> release process and release criterias.
+1 to that.
> We could
> a: allow more patches , e.g. I thing that this patch would be have
>
On 05/12/2016 10:06 AM, Cornelia Huck wrote:
> On Thu, 12 May 2016 09:40:21 +0200
> Christian Borntraeger wrote:
>
>> Maybe a topic for this years QEMU summit could be to talk about
>> release process and release criterias.
>
> +1 to that.
>
>> We could
>> a: allow
On 12 May 2016 at 08:40, Christian Borntraeger wrote:
> Maybe a topic for this years QEMU summit could be to talk about
> release process and release criterias.
Yeah, I'm happy to talk about what we could do better with
releases (both on the mailing list and at the
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Thursday, May 12, 2016 6:06 AM
>
> On Wed, 11 May 2016 17:15:15 +0800
> Jike Song wrote:
>
> > On 05/11/2016 12:02 AM, Neo Jia wrote:
> > > On Tue, May 10, 2016 at 03:52:27PM +0800, Jike Song wrote:
> > >>
From: Eric Blake
As mentioned in previous patches, we want to call visit_end_struct()
functions unconditionally, so that visitors can release resources
tied up since the matching visit_start_struct() without also having
to worry about error priority if more than one error
From: Eric Blake
Now that the QMP output visitor supports an explicit null
output, we should utilize it to make it easier to diagnose
the difference between a missing fdt ('null') vs. a
present-but-empty one ('{}').
(Note that this reverts the behavior of commit ab8bf1d,
From: Eric Blake
Right now, qmp-output-visitor happens to produce a QNull result
if nothing is actually visited between the creation of the visitor
and the request for the resulting QObject. A stronger protocol
would require that a QMP output visit MUST visit something. But
From: Eric Blake
Tighten assertions in the QMP output visitor, so that:
- qmp_output_get_qobject() can only be called after pairing a
visit_end_* for every visit_start_* (rather than allowing it on
a partially built object)
- qmp_output_get_qobject() cannot be called unless
From: Eric Blake
Add a new test, for checking reference counting of qnull(). As
part of the new file, move a previous reference counting change
added in commit a861564 to a more logical place.
Note that while most of the check-q*.c leave visitor stuff to
the
From: Eric Blake
The semantics of the list visit are somewhat baroque, with the
following pseudocode when FooList is used:
start()
for (prev = head; cur = next(prev); prev = ) {
visit(>value)
}
Note that these semantics (advance before visit) requires that
the first call
From: Eric Blake
Commit e8316d7 mistakenly passed consume=true within
qmp_input_optional() when checking if an optional member was
present, but the mistake was silently ignored since the code
happily let us extract a member more than once. Fix
qmp_input_optional() to not
From: Eric Blake
Returning a partial object on error is an invitation for a careless
caller to leak memory. We already fixed things in an earlier
patch to guarantee NULL if visit_start fails ("qapi: Guarantee
NULL obj on input visitor callback error"), but that does not
help
From: Eric Blake
Management of the top of stack was a bit verbose; creating a
temporary variable and adding some comments makes the existing
code more legible before the next few patches improve things.
No semantic changes other than asserting that we are always
visiting a
From: Eric Blake
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
On 2016年05月12日 14:49, Zhang Chen wrote:
On 05/09/2016 06:49 PM, Zhang Chen wrote:
+
+s->chr_sec_in = qemu_chr_find(s->sec_indev);
+if (s->chr_sec_in == NULL) {
+error_setg(errp, "Secondary IN Device '%s' not found",
+ s->sec_indev);
+return;
+
From: Eric Blake
The qmp-input visitor was allowing callers to play rather fast
and loose: when visiting a QDict, you could grab members of the
root dictionary without first pushing into the dict; among the
culprit callers was the generated marshal code on the 'arguments'
From: Eric Blake
Our existing input visitors were not very consistent on errors in a
function taking 'TYPE **obj'. These are start_struct(),
start_alternate(), type_str(), and type_any(). next_list() is
similar, but can't fail (see commit 08f9541). While all of them set
From: Eric Blake
We have three classes of QAPI visitors: input, output, and dealloc.
Currently, all implementations of these visitors have one thing in
common based on their visitor type: the implementation used for the
visit_type_enum() callback. But since we plan to add
From: Eric Blake
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
From: Eric Blake
The visitor interface for mapping between QObject/QemuOpts/string
and QAPI is scandalously under-documented, making changes to visitor
core, individual visitors, and users of visitors difficult to
coordinate. Among other questions: when is it safe to pass
From: Eric Blake
The following uses of a QMP input visitor should be strict
(that is, excess keys in QDict input should be flagged if not
converted to QAPI):
- Testsuite code unrelated to explicitly testing non-strict
mode (test-qmp-commands, test-visitor-serialization);
From: Eric Blake
Implement the new type_null() callback for the qmp input and
output visitors. While we don't yet have a use for this in QAPI
input (the generator will need some tweaks first), some
potential usages have already been discussed on the list.
Meanwhile, the output
The following changes since commit bfc766d38e1fae5767d43845c15c79ac8fa6d6af:
Update version for v2.6.0 release (2016-05-11 16:44:26 +0100)
are available in the git repository at:
git://repo.or.cz/qemu/armbru.git tags/pull-qapi-2016-05-12
for you to fetch changes up to
Add two negative tests, one for int and one for int16List. The latter
exposes a bug: nonsensical input results in an empty list instead of
an error.
Signed-off-by: Markus Armbruster
Message-Id: <1461325048-14122-1-git-send-email-arm...@redhat.com>
Signed-off-by: Eric Blake
From: Eric Blake
Ever since QMP was first added back in commit 43c20a43, we have
never had any QmpCommandType other than QCT_NORMAL. It's
pointless to carry around the cruft.
Signed-off-by: Eric Blake
Message-Id:
From: Eric Blake
As shown in the previous commit, the string input visitor was
treating bogus input as an empty list rather than an error.
Fix parse_str() to set errp, then the callers to exit early if
an error was reported.
Meanwhile, fix the testsuite to use the generated
From: Eric Blake
Rather than having two separate ways to create a QMP input
visitor, where the safer approach has the more verbose name,
it is better to consolidate things into a single function
where the caller must explicitly choose whether to be strict
or to ignore excess
From: Eric Blake
The qmp-input visitor was allowing callers to play rather fast
and loose: when visiting a QDict, you could grab members of the
root dictionary without first pushing into the dict; the final
such culprit was the QOM code for converting to and from object
From: Eric Blake
Don't embed the root of the visit into the stack of current
containers being visited. That way, we no longer get confused
on whether the first visit of a dictionary is to the dictionary
itself or to one of the members of the dictionary, based on
whether the
On 06.05.2016 12:30, Laurent Vivier wrote:
> Add myself to be the M68K maintainer.
>
> Signed-off-by: Laurent Vivier
> ---
> MAINTAINERS | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 81e7fac..c79404c 100644
> ---
On Thu, May 12, 2016 at 03:32:03PM +0800, Peter Xu wrote:
> On Thu, May 12, 2016 at 10:11:31AM +0300, Michael S. Tsirkin wrote:
> > On Wed, May 11, 2016 at 02:53:18PM +0800, Peter Xu wrote:
> > > On Wed, May 11, 2016 at 02:40:30PM +0800, Peter Xu wrote:
> > > > Recently I encountered issue when
On Wed, May 11, 2016 at 04:39:42PM -0600, Eric Blake wrote:
> The NBD protocol allows servers to advertise a human-readable
> description alongside an export name during NBD_OPT_LIST. Add
> an option to pass through the user's string to the NBD client.
>
> Doing this also makes it easier to test
Eduardo Habkost writes:
> On Wed, May 11, 2016 at 09:11:33AM +0200, Markus Armbruster wrote:
>> Eduardo Habkost writes:
>>
>> > On Tue, May 10, 2016 at 10:23:16AM +0200, Markus Armbruster wrote:
>> >> Eduardo Habkost writes:
>> >>
On 05/12/2016 12:41 AM, Peter Maydell wrote:
> On 11 May 2016 at 20:28, Christian Borntraeger wrote:
>> On 05/09/2016 07:57 PM, Peter Maydell wrote:
>>> On 9 May 2016 at 18:55, Peter Maydell wrote:
On 9 May 2016 at 18:53, Stefan Weil
On Wed, May 11, 2016 at 02:46:06PM -0500, miny...@acm.org wrote:
> From: Corey Minyard
>
> Signed-off-by: Corey Minyard
> ---
> hw/ipmi/smbus_ipmi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/hw/ipmi/smbus_ipmi.c b/hw/ipmi/smbus_ipmi.c
>
On Wed, May 11, 2016 at 02:46:05PM -0500, miny...@acm.org wrote:
> From: Corey Minyard
>
> Signed-off-by: Corey Minyard
> ---
> hw/acpi/ipmi.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/hw/acpi/ipmi.c b/hw/acpi/ipmi.c
On Thu, May 12, 2016 at 10:11:31AM +0300, Michael S. Tsirkin wrote:
> On Wed, May 11, 2016 at 02:53:18PM +0800, Peter Xu wrote:
> > On Wed, May 11, 2016 at 02:40:30PM +0800, Peter Xu wrote:
> > > Recently I encountered issue when debugging Intel IOMMU IR codes,
> > > that interrupts are not
On Wed, May 11, 2016 at 02:46:04PM -0500, miny...@acm.org wrote:
> From: Corey Minyard
>
> Signed-off-by: Corey Minyard
> ---
> hw/acpi/aml-build.c | 42 ++
> include/hw/acpi/aml-build.h | 11 +++
Fixes the remaining gtk 3.20 warnings.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Cole Robinson
Tested-by: Cole Robinson
---
ui/gtk.c | 49 +++--
1 file changed, 43 insertions(+), 6
On Wed, May 11, 2016 at 16:35:50 -0300, Eduardo Habkost wrote:
> # @CpuDefinitionInfo:
> #
> # Virtual CPU definition.
> #
> # @name: the name of the CPU definition
> # @runnable: #optional. whether the CPU model us usable with the
s/ us / is /
> #current machine and accelerator.
On Wed, May 11, 2016 at 02:53:18PM +0800, Peter Xu wrote:
> On Wed, May 11, 2016 at 02:40:30PM +0800, Peter Xu wrote:
> > Recently I encountered issue when debugging Intel IOMMU IR codes,
> > that interrupts are not working correctly with PCI bridges (reported
> > by Radim). This patch fixes the
On Wed, May 11, 2016 at 08:28:59PM -0300, Eduardo Habkost wrote:
> On Thu, May 12, 2016 at 12:51:55AM +0300, Michael S. Tsirkin wrote:
> > On Wed, May 11, 2016 at 03:50:39PM +0200, Igor Mammedov wrote:
> > > On Tue, 10 May 2016 17:24:14 -0300
> > > Eduardo Habkost wrote:
> >
On Wed, May 11, 2016 at 08:36:00PM -0300, Eduardo Habkost wrote:
> On Wed, May 11, 2016 at 03:50:39PM +0200, Igor Mammedov wrote:
> > On Tue, 10 May 2016 17:24:14 -0300
> > Eduardo Habkost wrote:
> >
> > > On Mon, May 02, 2016 at 02:33:21PM +0200, Igor Mammedov wrote:
> > >
On 05/09/2016 06:49 PM, Zhang Chen wrote:
+
+s->chr_sec_in = qemu_chr_find(s->sec_indev);
+if (s->chr_sec_in == NULL) {
+error_setg(errp, "Secondary IN Device '%s' not found",
+ s->sec_indev);
+return;
+}
+
+s->chr_out =
> Updated to:
>
> ##
> # @CpuDefinitionInfo:
> #
> # Virtual CPU definition.
> #
> # @name: the name of the CPU definition
> # @runnable: #optional. whether the CPU model us usable with the
> #current machine and accelerator. Omitted if we don't
> #know the answer. (since
On 05/12/2016 09:11 AM, Jason Wang wrote:
On 2016年05月11日 19:20, Zhang Chen wrote:
On 05/11/2016 05:01 PM, Jason Wang wrote:
On 2016年05月06日 18:56, Zhang Chen wrote:
Signed-off-by: Zhang Chen
Signed-off-by: Li Zhijian
301 - 383 of 383 matches
Mail list logo