include:
1. remove unnecessary declaration of static function
2. fix inconsistency between comment and function name, and typo OOM->QOM
2. update comments of functions, use uniform format(GTK-Doc style)
Signed-off-by: Cao jin
---
changelog:
1. Use uniform comment format. (Markus)
2. Update functi
Hello all:
I am very sorry for delay finishing tilegx floating points insns.
The reason is that during these days (I guess, until 2016-05-01), I have
no any free time.
- During these days, I am often not at home (sleep in a hotel near the
office), and often work in the weekend.
- It is abo
On Sat, Apr 16, 2016 at 07:44:12PM -0700, Jan Kiszka wrote:
> On 2016-04-14 20:31, Peter Xu wrote:
> > This patch allows Intel IR work with splitted irqchip. Two more fields
> > are added to IOAPICCommonState to support the translation process (For
> > future AMD IR support, we will need to provide
If an application uses libmtp on the guest system,
it will complain with the warning message:
LIBMTP WARNING: VendorExtensionID:
LIBMTP WARNING: VendorExtensionDesc: (null)
LIBMTP WARNING: this typically means the device is PTP (i.e. a camera) but
not a MTP device at all. Trying to continu
This patch causes a regression in FreeBSD guests. Kernel dmesg reports:
usbus3: Run timeout
ehci0: USB init failed err=18
and USB 2.0 passthrough does not work. USB 1.0 still works though.
On a (possibly) related note, choosing any machine type above
pc-i440fx-2.0 causes 100% CPU in host.
Hi, Leon,
I cannot say thank you enough for all your valuable feedback.
Just wanted to give you a heads up that in the next version of this patch
series (planned for tomorrow (Monday) or the day after tomorrow), I am going to
integrate all your suggestions from this thread, including name "stat
On Wed, Apr 13, 2016 at 05:09:49PM +0800, Fam Zheng wrote:
> Underneath is the fcntl syscall that locks the local file, similar to what is
> already used in libvirt virtlockd. Also because of that, we cannot directly
> apply fcntl lock on the image file itself, instead we open and lock
> "/var/tm
On Fri, Apr 15, 2016 at 11:27:55AM +0800, Fam Zheng wrote:
> virtlockd in libvirt locks the first byte, we lock byte 1 to avoid
> the intervene.
> +static int raw_lockf(BlockDriverState *bs, BdrvLockfCmd cmd)
> +{
> +
> +BDRVRawState *s = bs->opaque;
> +int ret;
> +struct flock fl = (st
Greg Kurz writes:
> On Tue, 15 Mar 2016 00:02:48 +0800
> Jevon Qiao wrote:
>
>> Ceph as a promising unified distributed storage system is widely used in the
>> world of OpenStack. OpenStack users deploying Ceph for block (Cinder) and
>> object (S3/Swift) are unsurprisingly looking at Manila and
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
---
ui/gtk.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/ui/gtk.c b/ui/gtk.c
index f372a6d..83af491 100644
--- a/ui/gtk.c
+++
On 04/16/16 01:31, Paolo Bonzini wrote:
>
> Right, but there's always the point about people that use heterogeneous
> hosts and cannot pass rdrand/rdseed to the guest. For these, we should
> add a QEMU driver that uses rdrand/rdseed, and thus decouples virtio-rng
> from the host /dev/* completely
On 04/16/16 01:31, Paolo Bonzini wrote:
>
> Right, but there's always the point about people that use heterogeneous
> hosts and cannot pass rdrand/rdseed to the guest. For these, we should
> add a QEMU driver that uses rdrand/rdseed, and thus decouples virtio-rng
> from the host /dev/* completely
On 04/17/2016 05:59 AM, Max Reitz wrote:
On 15.04.2016 07:46, Changlong Xie wrote:
Qemu does not support "info blockstats" now.
It doesn't? Mine is more than happy to accept that command:
$ x86_64-softmmu/qemu-system-x86_64 -nodefaults \
-drive if=none,id=drv0,driver=null-co \
-moni
On 04/17/2016 06:11 AM, Max Reitz wrote:
I'd like to say that my inertia is keeping me from applying this patch,
but I'd feel like a hypocrite for saying that, considering it would have
taken much less time than writing this response...
Pls feel free to ignore this patch, i just went through ke
On Sun, 04/17 20:27, Richard W.M. Jones wrote:
> On Fri, Apr 15, 2016 at 11:27:55AM +0800, Fam Zheng wrote:
> > virtlockd in libvirt locks the first byte, we lock byte 1 to avoid
> > the intervene.
> > +static int raw_lockf(BlockDriverState *bs, BdrvLockfCmd cmd)
> > +{
> > +
> > +BDRVRawState
On Sat, 04/16 16:29, Denis V. Lunev wrote:
> On 04/15/2016 06:27 AM, Fam Zheng wrote:
> >virtlockd in libvirt locks the first byte, we lock byte 1 to avoid
> >the intervene.
> >
> >Suggested-by: "Daniel P. Berrange"
> >Signed-off-by: Fam Zheng
> >---
> > block/raw-posix.c | 35 ++
On Sun, 04/17 01:29, Max Reitz wrote:
> On 15.04.2016 05:27, Fam Zheng wrote:
> > 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 | 42 +
On Fri, 04/15 17:11, Kevin Wolf wrote:
> Am 15.04.2016 um 05:11 hat Fam Zheng geschrieben:
> > qcow2 is not necessarily the top layer node. Since bdrv_inactivate()
> > doesn't recurse, we should ensure all block nodes are inactivated.
> >
> > Signed-off-by: Fam Zheng
>
> Hm, I don't think that's
On Sat, 04/16 16:22, Denis V. Lunev wrote:
> On 04/15/2016 06:27 AM, Fam Zheng wrote:
> >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 | 42 +++
On Sat, Apr 16, 2016 at 07:30:25PM -0700, Jan Kiszka wrote:
> On 2016-04-14 20:31, Peter Xu wrote:
> > Enable IR in IOMMU Extended Capability register.
> >
> > Signed-off-by: Peter Xu
> > ---
> > hw/i386/intel_iommu.c | 7 +++
> > hw/i386/intel_iommu_internal.h | 2 ++
> > 2 files c
On Sat, Apr 16, 2016 at 07:26:50PM -0700, Jan Kiszka wrote:
> Hi Peter,
>
> series no longer applies to git master. What was the baseline? Do you
> have a public git repo as well?
Yep, since I missed the first patch. Please check v4 later. Sorry!
-- peterx
On Fri, Apr 15, 2016 at 05:31:58PM +0200, Radim Krčmář wrote:
> 2016-04-15 11:31+0800, Peter Xu:
> > This patch allows Intel IR work with splitted irqchip. Two more fields
> > are added to IOAPICCommonState to support the translation process (For
> > future AMD IR support, we will need to provide a
On Fri, 2016-15-04 at 02:06:13 UTC, Unknown sender due to SPF wrote:
> The real LE feature entry in the ibm_pa_feature struct has the
> wrong number of elements. Instead of checking for byte 5, bit 0,
> we check for byte 0, bit 0, and we also incorrectly update cpu user
> feature bit 5.
>
> diff -
On Sat, 2016-04-16 at 00:27 +1000, Michael Ellerman wrote:
> On Fri, 2016-15-04 at 02:06:13 UTC, Unknown sender due to SPF wrote:
> > The real LE feature entry in the ibm_pa_feature struct has the
> > wrong number of elements. Instead of checking for byte 5, bit 0,
> > we check for byte 0, bit 0, a
On Fri, Apr 15, 2016 at 11:03:00AM +0200, Thomas Huth wrote:
> env->xer only holds the lower bits of the XER register nowadays, the
> SO, OV and CA bits are stored in separate variables (see the function
> cpu_write_xer() for details). Since the migration code currently only
> reads the "xer" varia
The following changes since commit c7b45f12828c1ba7105dbc029c63d7de68eaa91c:
Merge remote-tracking branch 'remotes/armbru/tags/pull-backends-2016-04-15'
into staging (2016-04-15 17:43:34 +0100)
are available in the git repository at:
git://github.com/dgibson/qemu.git tags/ppc-for-2.6-201604
From: Thomas Huth
There are two issues: First, the number of registers that are used has
to be calculated with "(nb + 3) / 4" (i.e. round always up, not down).
Second, the "start <= ra && (start + nr - 32) > ra" condition for the
wrap-around case is wrong: It has to be tested with "||" instead of
From: Thomas Huth
The range checks in the LSWX instruction are completely insufficient:
They do not take the wrap-around case into account, and the check
"reg < rx" should be "reg <= rx" instead. Fix it by using the new
lsw_reg_in_range() helper function that is already used for LSWI, too.
Then
From: Thomas Huth
env->xer only holds the lower bits of the XER register nowadays, the
SO, OV and CA bits are stored in separate variables (see the function
cpu_write_xer() for details). Since the migration code currently only
reads the "xer" variable, the upper bits are lost during migration.
Fi
On 04/18/2016 04:12 AM, Fam Zheng wrote:
On Sat, 04/16 16:29, Denis V. Lunev wrote:
On 04/15/2016 06:27 AM, Fam Zheng wrote:
virtlockd in libvirt locks the first byte, we lock byte 1 to avoid
the intervene.
Suggested-by: "Daniel P. Berrange"
Signed-off-by: Fam Zheng
---
block/raw-posix.c |
On 04/18/2016 04:33 AM, Fam Zheng wrote:
On Sun, 04/17 01:29, Max Reitz wrote:
On 15.04.2016 05:27, Fam Zheng wrote:
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 | 4
Cao jin writes:
> include:
> 1. remove unnecessary declaration of static function
> 2. fix inconsistency between comment and function name, and typo OOM->QOM
> 2. update comments of functions, use uniform format(GTK-Doc style)
>
> Signed-off-by: Cao jin
Reviewed-by: Markus Armbruster
Hi,
> Vnc already uses qemu_input_event_send_key_delay today, so I'm not sure
> where things fall apart.
Well, not everywhere. Try the attached patch.
Also worth trying:
* use xhci instead of ohci (current slof should handle
kbd-via-xhci fine)
* use virtio-keyboard (no slof driver yet a
33 matches
Mail list logo
