Am 27.11.2010 08:12, schrieb Stefan Hajnoczi:
> On Fri, Nov 26, 2010 at 9:59 PM, Christian Brunner
> wrote:
>> Thanks for the review. What am I supposed to do now?
>
> Kevin is the block maintainer. His review is the next step, I have
> CCed him. After that rbd would be ready to merge.
If I do
Am 28.11.2010 12:55, schrieb Yoshiaki Tamura:
> 2010/11/28 Michael S. Tsirkin :
>> On Thu, Nov 25, 2010 at 03:06:52PM +0900, Yoshiaki Tamura wrote:
>>> Replace bdrv_aio_writev() with bdrv_aio_writev_proxy() to let
>>> event-tap capture events from dma-helpers.
>>>
>>> Signed-off-by: Yoshiaki Tamura
On 11/26/10 16:19, Alexander Graf wrote:
>
> On 26.11.2010, at 16:10, Peter Maydell wrote:
>
>> On 26 November 2010 14:21, Anthony Liguori wrote:
>>
>>> But the key point is breadth, it should not be a "KVM Forum" but rather an
>>> Open Virtualization conference with topics as high level as clou
Am 29.11.2010 09:59, schrieb Kevin Wolf:
> Am 27.11.2010 08:12, schrieb Stefan Hajnoczi:
>> On Fri, Nov 26, 2010 at 9:59 PM, Christian Brunner
>> wrote:
>>> Thanks for the review. What am I supposed to do now?
>>
>> Kevin is the block maintainer. His review is the next step, I have
>> CCed him.
Hi All,
Now that I have usb-1.1 passthrough / local redirection support
working reliably (see my patch sets for this), I'm going to start
working on doing usb redirection support over the network.
The idea here is that a usb device connected to machine a, will be
available for use by the guest
On Fri, 26 Nov 2010, Anthony Liguori wrote:
> On 11/26/2010 08:15 AM, Jes Sorensen wrote:
> > I would be all in favor of this! Do you want to attach it to another
> > conference or totally standalone?
> >
>
> Attaching is easier logistically but I don't know how much that helps if
> it's a fu
On Sat, Nov 27, 2010 at 1:11 PM, Yoshiaki Tamura
wrote:
> 2010/11/27 Stefan Hajnoczi :
>> On Sat, Nov 27, 2010 at 8:53 AM, Yoshiaki Tamura
>> wrote:
>>> 2010/11/27 Stefan Hajnoczi :
On Sat, Nov 27, 2010 at 4:29 AM, Yoshiaki Tamura
wrote:
> 2010/11/27 Blue Swirl :
>> On Thu, Nov
Hi,
BTW are you actually aware of any option rom with multiple BCVs and, if
yes, how those BCVs differ?
Multiple BCVs - yes. A SCSI card will define a BCV for each attached
drive. I don't have a scsi card myself, but the support was added by
a user who ran into the problem first hand.
FY
Your report is incomplete.
Please provide your configure line, and also what system your are
compiling on.
In addition, please try building top of tree qemu with this configure
line.
Thanks,
Jes
** Changed in: qemu
Status: New => Incomplete
--
fail to compile qemu-kvm-0.13.0
https://b
Hi,
If scsi card has optionrom with only one bcv then Seabios can determine
its boot order from device path, so why not provide user with this
option today?
It's unclear to me how SeaBIOS is supposed to do that.
Try to keep track of which bcv/bev belongs to which pci device? It
should su
On Thu, Nov 25, 2010 at 6:06 AM, Yoshiaki Tamura
wrote:
> event-tap controls when to start FT transaction, and provides proxy
> functions to called from net/block devices. While FT transaction, it
> queues up net/block requests, and flush them when the transaction gets
> completed.
>
> Signed-off
Hi,
Doesn't make that much sense IMHO as the both provide quite simliar
informations (i.e. "info spice" gives you a list of connections with
pretty much the same info provided by the events).
If you are wanting to record/log incoming connections, then you
can't use 'info spice' to get the de
The current default of 16 buffers for the control vq is too small for
the default max_nr_ports of 32. We can get more entries in there,
example when asking the guest to add max. allowed ports.
Default to using the minimum required (next power of 2) of the
max_nr_ports in use.
Signed-off-by: Amit
On 11/26/2010 03:21 PM, Anthony Liguori wrote:
But the key point is breadth, it should not be a "KVM Forum" but rather
an Open Virtualization conference with topics as high level as cloud
software automation and as low level as asynchronous page faults :-)
That would really be cool, and it woul
Hi,
The idea here is that a usb device connected to machine a, will be
available for use by the guest os running on host b (machine b).
I'm working on this because it is something which we want / need
for spice. I'm wondering if there is interest in this outside
of spice ?
Sure. The idea t
On Mon, Nov 29, 2010 at 11:19:29AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> >>BTW are you actually aware of any option rom with multiple BCVs and, if
> >>yes, how those BCVs differ?
> >
> >Multiple BCVs - yes. A SCSI card will define a BCV for each attached
> >drive. I don't have a scsi card myse
On 28.11.2010, at 16:59, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Xen target bits in qemu are intended for x86. Let the build system
> reflect this and avoid useless building/linking for other targets.
Not sure I understand the split. Xen is x86 only, yes. But why split it into
host and targe
Am 29.11.2010 13:24, Alexander Graf wrote:
>
> On 28.11.2010, at 16:59, Jan Kiszka wrote:
>
>> From: Jan Kiszka
>>
>> Xen target bits in qemu are intended for x86. Let the build system
>> reflect this and avoid useless building/linking for other targets.
>
> Not sure I understand the split. Xen
Am 29.11.2010 11:11, Hans de Goede wrote:
> Hi All,
>
> Now that I have usb-1.1 passthrough / local redirection support
> working reliably (see my patch sets for this), I'm going to start
> working on doing usb redirection support over the network.
>
> The idea here is that a usb device connecte
On 29.11.2010, at 13:30, Jan Kiszka wrote:
> Am 29.11.2010 13:24, Alexander Graf wrote:
>>
>> On 28.11.2010, at 16:59, Jan Kiszka wrote:
>>
>>> From: Jan Kiszka
>>>
>>> Xen target bits in qemu are intended for x86. Let the build system
>>> reflect this and avoid useless building/linking for o
Am 29.11.2010 13:40, Alexander Graf wrote:
>
> On 29.11.2010, at 13:30, Jan Kiszka wrote:
>
>> Am 29.11.2010 13:24, Alexander Graf wrote:
>>>
>>> On 28.11.2010, at 16:59, Jan Kiszka wrote:
>>>
From: Jan Kiszka
Xen target bits in qemu are intended for x86. Let the build system
2010/11/29 Kevin Wolf :
> Am 28.11.2010 12:55, schrieb Yoshiaki Tamura:
>> 2010/11/28 Michael S. Tsirkin :
>>> On Thu, Nov 25, 2010 at 03:06:52PM +0900, Yoshiaki Tamura wrote:
Replace bdrv_aio_writev() with bdrv_aio_writev_proxy() to let
event-tap capture events from dma-helpers.
>>>
> >> Could you formulate the constraints so developers are aware of them in
> >> the future and can protect the codebase. How about expanding the
> >> Kemari wiki pages?
> >
> > If you like the idea above, I'm happy to make the list also on
> > the wiki page.
>
> Here's a different question: wha
2010/11/29 Paul Brook :
>> >> Could you formulate the constraints so developers are aware of them in
>> >> the future and can protect the codebase. How about expanding the
>> >> Kemari wiki pages?
>> >
>> > If you like the idea above, I'm happy to make the list also on
>> > the wiki page.
>>
>> He
> 2010/11/29 Paul Brook :
> >> >> Could you formulate the constraints so developers are aware of them
> >> >> in the future and can protect the codebase. How about expanding the
> >> >> Kemari wiki pages?
> >> >
> >> > If you like the idea above, I'm happy to make the list also on
> >> > the wiki
2010/11/29 Paul Brook :
>> 2010/11/29 Paul Brook :
>> >> >> Could you formulate the constraints so developers are aware of them
>> >> >> in the future and can protect the codebase. How about expanding the
>> >> >> Kemari wiki pages?
>> >> >
>> >> > If you like the idea above, I'm happy to make the
2010/11/29 Alexander Graf :
> Nathan and Peter, are you two going anyways, despite giving a talk or not?
I will be going regardless, yes.
-- PMM
> >> To answer Stefan's question, there shouldn't be any requirement
> >> for a device, but must be tested with Kemari. If it doesn't work
> >> correctly, the problems must be fixed before adding to the list.
> >
> > What exactly are the problems? Is this a device bus of a Kemari bug?
> > If it's
On 29.11.2010, at 13:44, Jan Kiszka wrote:
> Am 29.11.2010 13:40, Alexander Graf wrote:
>>
>> On 29.11.2010, at 13:30, Jan Kiszka wrote:
>>
>>> Am 29.11.2010 13:24, Alexander Graf wrote:
On 28.11.2010, at 16:59, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Xen target
On 23.11.2010, at 20:51, anthony.per...@citrix.com wrote:
> From: Anthony PERARD
>
> Hi all,
>
> Here is the V7 of the patch series that adds Xen device model support in QEMU.
>
> The change made on it since the v6:
> - I introduce a patch from Alexander Graf to add a generic layer for the X
On 29.11.2010, at 07:43, Frédéric Pétrot wrote:
> Nathan Froyd a écrit :
>> On Sun, Nov 28, 2010 at 09:20:25AM +0100, Frédéric Pétrot wrote:
>>> IMHO someone from code sourcery would be great, as they (Paul Brooks in
>>> the
>>> older versions, it seems that Nathan is now taking over) are co
Am 29.11.2010 15:15, Alexander Graf wrote:
>
> On 29.11.2010, at 13:44, Jan Kiszka wrote:
>
>> Am 29.11.2010 13:40, Alexander Graf wrote:
>>>
>>> On 29.11.2010, at 13:30, Jan Kiszka wrote:
>>>
Am 29.11.2010 13:24, Alexander Graf wrote:
>
> On 28.11.2010, at 16:59, Jan Kiszka wrote:
>
On 29.11.2010, at 15:27, Jan Kiszka wrote:
> Am 29.11.2010 15:15, Alexander Graf wrote:
>>
>> On 29.11.2010, at 13:44, Jan Kiszka wrote:
>>
>>> Am 29.11.2010 13:40, Alexander Graf wrote:
On 29.11.2010, at 13:30, Jan Kiszka wrote:
> Am 29.11.2010 13:24, Alexander Graf wrote:
>
> Hi All,
>
> Now that I have usb-1.1 passthrough / local redirection support
> working reliably (see my patch sets for this), I'm going to start
> working on doing usb redirection support over the network.
>
> The idea here is that a usb device connected to machine a, will be
> available for
On 11/28/2010 04:56 AM, Alexander Graf wrote:
On 28.11.2010, at 01:17, Nathan Froyd wrote:
On Fri, Nov 26, 2010 at 01:26:31AM +0100, François Revol wrote:
the people we are addressing and we would like to bring together is from the
QEMU emulation community.
We are interested in runn
Does anyone know of a tool that convert texi to wiki syntax or know
enough about texi parsing that something could be rigged up?
Even if it takes a couple steps, like texi2xml, then xml->wiki, that
would be workable. I'm willing to do some leg work but I don't want to
write a texi parser from
2010/11/29 Paul Brook :
>> >> To answer Stefan's question, there shouldn't be any requirement
>> >> for a device, but must be tested with Kemari. If it doesn't work
>> >> correctly, the problems must be fixed before adding to the list.
>> >
>> > What exactly are the problems? Is this a device bus
Hello All,
I am running QEMU Arm emulation on x86_64 machine. I downloaded the
arm-test kernel and the initrd image available on QEMU download site.
When I run the qemu-system-arm with the memory less than or equal to
256M everything works fine.
pra...@prasad-desktop:~/Downloads/arm-test$ qemu-sy
> > If devices incorrectly claim support for live migration, then that should
> > also be fixed, either by removing the broken code or by making it work.
>
> I totally agree with you.
>
> > AFAICT your current proposal is just feeding back the results of some
> > fairly specific QA testing. I'd
On Mon, Nov 29, 2010 at 08:34:28AM -0600, Anthony Liguori wrote:
> On 11/28/2010 04:56 AM, Alexander Graf wrote:
>> On 28.11.2010, at 01:17, Nathan Froyd wrote:
>>> We (CodeSourcery) are very interested in Windows host support. (We
>>> distribute QEMU with our commerical development products for
>
2010/11/29 Paul Brook :
>> > If devices incorrectly claim support for live migration, then that should
>> > also be fixed, either by removing the broken code or by making it work.
>>
>> I totally agree with you.
>>
>> > AFAICT your current proposal is just feeding back the results of some
>> > fair
Paul Brook writes:
>> > Likewise requiring separate tracing hooks be added to the existing
>> > decoders is extremely unlikely to be a feasible long-term
>> > solution.
>>
>> You mean having to modify each "translate.c"? The worst event to handle
>> is instruction fetch on x86.
> Instruction fet
Frederick,
please let me know if you can confirm that this patch fixes it for you. If you
need
me to set up a ppa with that patch, please let me know.
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of qemu-
devel-ml
@earl,
thanks for finding the specific patch!
--
virsh save is very slow
https://bugs.launchpad.net/bugs/524447
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in libvirt virtualization API: Unknown
Status in QEMU: Invalid
Statu
On Mon, 29 Nov 2010, Alexander Graf wrote:
>
> On 23.11.2010, at 20:51, anthony.per...@citrix.com wrote:
>
> > From: Anthony PERARD
> >
> > Hi all,
> >
> > Here is the V7 of the patch series that adds Xen device model support in
> > QEMU.
> >
> > The change made on it since the v6:
> > - I intr
On 29 November 2010 14:37, Prasad Joshi wrote:
> I am running QEMU Arm emulation on x86_64 machine. I downloaded the
> arm-test kernel and the initrd image available on QEMU download site.
>
> When I run the qemu-system-arm with the memory less than or equal to
> 256M everything works fine.
> pra.
On Mon, Nov 29, 2010 at 02:58:57PM +0100, Alexander Graf wrote:
> > Nathan Froyd a écrit :
> >> I'm sorry, what are the "both talks" you refer to above? Are you
> >> proposing an additional talk alongside your (Frédéric's) existing talk?
> >
> > No! I am very happy that you take over the introdu
Avoid sending out packets, and modifying
device state, when VM is stopped.
Add assert statements to verify this does not happen.
Avoid scheduling bh when vhost-net is started.
Stop bh when driver disabled bus mastering
(we must not access memory after this).
Signed-off-by: Michael S. Tsirkin
-
On 29.11.2010, at 16:10, Anthony PERARD wrote:
> On Mon, 29 Nov 2010, Alexander Graf wrote:
>
>>
>> On 23.11.2010, at 20:51, anthony.per...@citrix.com wrote:
>>
>>> From: Anthony PERARD
>>>
>>> Hi all,
>>>
>>> Here is the V7 of the patch series that adds Xen device model support in
>>> QEM
On Mon, Nov 29, 2010 at 3:13 PM, Peter Maydell wrote:
> On 29 November 2010 14:37, Prasad Joshi wrote:
>> I am running QEMU Arm emulation on x86_64 machine. I downloaded the
>> arm-test kernel and the initrd image available on QEMU download site.
>>
>> When I run the qemu-system-arm with the memo
Hi,
Not me at the moment, but unless you tunnel it inside another
protocol, you'd really want to look at the existing USB-over-IP
protocols instead of reinventing the wheel:
http://usbip.sourceforge.net/ (some support in Linux already IIRC)
(and there are others which I don't recall)
Doesn't
On 29 November 2010 15:45, Prasad Joshi wrote:
> I tried to emulate few other boards as well. IMHO, versatilepb
> supports more than 256M RAM, I guess it supports upto 512MB. But it
> too fails
No, 'versatilepb' also supports only 256MB of RAM, for the
same reason (system registers starting at 0x
> >> Sorry, I didn't get what you're trying to tell me. My plan would
> >> be to initially start from a subset of devices, and gradually
> >> grow the number of devices that Kemari works with. While this
> >> process, it'll include what you said above, file a but and/or fix
> >> the code. Am I m
Hi,
This patch series is the start for an overhaul of the usb descriptor
handling for emulated usb devices. Instead of storing the device
desriptors in blobs (aka char arrays) they are stored in structs,
which makes it alot easier to work with them. This in turn allows
to move common device ma
Switch the usb wavom driver over to the
new descriptor infrastructure.
Signed-off-by: Gerd Hoffmann
---
hw/usb-wacom.c | 175 +++-
1 files changed, 71 insertions(+), 104 deletions(-)
diff --git a/hw/usb-wacom.c b/hw/usb-wacom.c
index 47f26cd.
Switch the usb serial drivers (serial, braille) over to the
new descriptor infrastructure.
Note that this removes the freely configurable vendor and product id
properties. I think the only reason this was configurable is that the
only difference between the serial and the braille device is the
ve
Switch the usb hid drivers (keyboard, mouse, tablet) over to the
new descriptor infrastructure.
Signed-off-by: Gerd Hoffmann
---
hw/usb-hid.c | 445 ++---
1 files changed, 203 insertions(+), 242 deletions(-)
diff --git a/hw/usb-hid.c b/hw/usb
If a serial number is present for the drive fill it into the usb
serialnumber string descriptor.
Signed-off-by: Gerd Hoffmann
---
hw/usb-msd.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/hw/usb-msd.c b/hw/usb-msd.c
index b049122..7b6a0d7 100644
--- a/hw/usb-msd.
Switch the usb hub driver over to the
new descriptor infrastructure.
It also removes the nr_ports variable and MAX_PORTS define and
introduces a NUM_PORTS define instead. The numver of ports was
(and still is) fixed at 8 anyway.
Signed-off-by: Gerd Hoffmann
---
hw/usb-hub.c | 141
Switch the usb network driver over to the
new descriptor infrastructure.
Signed-off-by: Gerd Hoffmann
---
hw/usb-net.c | 450 +++---
1 files changed, 207 insertions(+), 243 deletions(-)
diff --git a/hw/usb-net.c b/hw/usb-net.c
index 54d23fb..
This patch adds hw/usb-desc.[ch] files. They carry data structures
for various usb descriptors and helper functions to generate usb
packets from the structures.
The intention is to have a internal representation of the device
desription which is more usable than the current char array blobs,
so w
USB_REQ_SET_ADDRESS handling is identical in *all* emulated devices.
Move it to common code.
Signed-off-by: Gerd Hoffmann
---
hw/usb-bt.c |4
hw/usb-desc.c |4
hw/usb-hid.c|4
hw/usb-hub.c|4
hw/usb-msd.c|4
hw/usb-net.c|5 --
This patch adds fields to the USBDevice struct for the current
speed (hard-wired to full speed for now) and current device
configuration. Also a init function is added which inializes
these fields. This allows USB_REQ_{GET,SET}_CONFIGURATION
handling to be moved to common code.
For most drivers
On Mon, 29 Nov 2010, Alexander Graf wrote:
>
> On 29.11.2010, at 16:10, Anthony PERARD wrote:
>
> > On Mon, 29 Nov 2010, Alexander Graf wrote:
> >
> >>
> >> On 23.11.2010, at 20:51, anthony.per...@citrix.com wrote:
> >>
> >>> From: Anthony PERARD
> >>>
> >>> Hi all,
> >>>
> >>> Here is the V7 of
This patch allows to set usb descriptor strings per device instance.
Signed-off-by: Gerd Hoffmann
---
hw/usb-bus.c |1 +
hw/usb-desc.c | 52
hw/usb-desc.h |4 +++-
hw/usb.h |9 +
4 files changed, 57 insertions(+), 9
On Mon, Nov 29, 2010 at 3:00 PM, Yoshiaki Tamura
wrote:
> 2010/11/29 Paul Brook :
>>> > If devices incorrectly claim support for live migration, then that should
>>> > also be fixed, either by removing the broken code or by making it work.
>>>
>>> I totally agree with you.
>>>
>>> > AFAICT your cu
> > Not me at the moment, but unless you tunnel it inside another
> > protocol, you'd really want to look at the existing USB-over-IP
> > protocols instead of reinventing the wheel:
> > http://usbip.sourceforge.net/ (some support in Linux already IIRC)
> > (and there are others which I don't recall
Switch the usb storage driver over to the
new descriptor infrastructure.
Signed-off-by: Gerd Hoffmann
---
hw/usb-msd.c | 164 +
1 files changed, 61 insertions(+), 103 deletions(-)
diff --git a/hw/usb-msd.c b/hw/usb-msd.c
index 0a95d8d..b0
Switch the usb bluetooth driver over to the
new descriptor infrastructure.
Signed-off-by: Gerd Hoffmann
---
hw/usb-bt.c | 470 +--
1 files changed, 200 insertions(+), 270 deletions(-)
diff --git a/hw/usb-bt.c b/hw/usb-bt.c
index 56d1a6c..
On Tue, Nov 23, 2010 at 06:53:45PM +, Peter Maydell wrote:
> Signed-off-by: Peter Maydell
Reviewed-by: Nathan Froyd
-Nathan
Hi,
I'm note sure about what I will say, but will a kernel approach
handle specific disconnection/reconnection of devices, that libusb
cannot?
Don't know, didn't investigate (yet) what libusb can do and what it can't.
cheers,
Gerd
On Tue, Nov 23, 2010 at 06:53:46PM +, Peter Maydell wrote:
> The ARM architecture mandates that converting a NaN value to
> integer gives zero (if Invalid Operation FP exceptions are
> not being trapped). This isn't the behaviour of the SoftFloat
> library, so NaNs must be special-cased.
>
> +
On 11/29/2010 06:23 PM, Stefan Hajnoczi wrote:
On Mon, Nov 29, 2010 at 3:00 PM, Yoshiaki Tamura
wrote:
2010/11/29 Paul Brook:
If devices incorrectly claim support for live migration, then that should
also be fixed, either by removing the broken code or by making it work.
I totally agree wit
On 29 November 2010 16:38, Nathan Froyd wrote:
>> +static int float32_is_any_nan(float32 x)
>> +{
>> + return ((float32_val(x) & ~(1 << 31)) > 0x7f80UL);
>> +}
>> +
>> +static int float64_is_any_nan(float64 x)
>> +{
>> + return ((float64_val(x) & ~(1ULL << 63)) > 0x7ff0ULL);
> > Is this a fair summary: any device that supports live migration workw
> > under Kemari?
>
> It might be fair summary but practically we barely have live migration
> working w/o Kemari. In addition, last I checked Kemari needs additional
> hooks and it will be too hard to keep that out of tree
On Mon, Nov 29, 2010 at 04:49:24PM +, Peter Maydell wrote:
> On 29 November 2010 16:38, Nathan Froyd wrote:
> > Why not just use:
> >
> > static int float32_is_any_nan(float32 x)
> > {
> > return float32_is_nan(x) || float32_is_signaling_nan(x);
> > }
> >
> > and likewise for the 64-bit case?
On 11/29/2010 10:53 AM, Paul Brook wrote:
Is this a fair summary: any device that supports live migration workw
under Kemari?
It might be fair summary but practically we barely have live migration
working w/o Kemari. In addition, last I checked Kemari needs additional
hooks and it will b
On Tue, Nov 23, 2010 at 06:53:41PM +, Peter Maydell wrote:
> From: Johan Bengtsson
>
> The thumb2 decoder contained a mixup between the bit controlling
> doubling and the bit controlling if the operation was an add or a sub.
>
> Signed-off-by: Johan Bengtsson
> Signed-off-by: Peter Maydell
On Tue, Nov 23, 2010 at 06:53:48PM +, Peter Maydell wrote:
> VCVT of 16 bit fixed point to float should ignore the top 16 bits
> of the source register. Cast to int16_t and friends rather than
> int16 -- the former is guaranteed exactly 16 bits wide where the
> latter is merely at least 16 bits
>Hi,
>
> > Not me at the moment, but unless you tunnel it inside another
> > protocol, you'd really want to look at the existing USB-over-IP
> > protocols instead of reinventing the wheel:
> > http://usbip.sourceforge.net/ (some support in Linux already IIRC)
> > (and there are others which I
> On 11/29/2010 10:53 AM, Paul Brook wrote:
> >>> Is this a fair summary: any device that supports live migration workw
> >>> under Kemari?
> >>
> >> It might be fair summary but practically we barely have live migration
> >> working w/o Kemari. In addition, last I checked Kemari needs additional
>>> The idea here is that a usb device connected to machine a, will be
>>> available for use by the guest os running on host b (machine b).
>>>
>>> I'm working on this because it is something which we want / need
>>> for spice. I'm wondering if there is interest in this outside
>>> of spice ?
>>>
On 11/29/2010 11:18 AM, Paul Brook wrote:
On 11/29/2010 10:53 AM, Paul Brook wrote:
Is this a fair summary: any device that supports live migration workw
under Kemari?
It might be fair summary but practically we barely have live migration
working w/o Kemari. In addition, last
Hi,
I guess it should be abstract enough to support multiple back-ends, be it a
kernel driver or through libusb?
Rgrds,
Attila
2010/11/29 Gerd Hoffmann
> Hi,
>
>
> I'm note sure about what I will say, but will a kernel approach
>> handle specific disconnection/reconnection of devices, tha
Hi,
0.13 was a mess of a release (largely due to my lack of time) and I'd
like to get us back onto a predictable schedule.
Here's what I propose:
12/6 - fork off stable-0.14 tree; simultaneously release qemu-0.14.0-rc0
For the stable-0.14 tree, I'd like to have Justin be in charge of
collec
On 11/29/2010 11:37 AM, Attila Sukosd wrote:
Hi,
I guess it should be abstract enough to support multiple back-ends, be
it a kernel driver or through libusb?
Is this something that should just live in libusb?
If what libusb presented QEMU was actually implemented as USB-over-IP,
QEMU wouldn
On Tue, Nov 23, 2010 at 06:53:47PM +, Peter Maydell wrote:
> The ARM ARM defines that if the input to a single<->double conversion
> is a NaN then the output is always forced to be a quiet NaN by setting
> the most significant bit of the fraction part.
>
> Signed-off-by: Peter Maydell
>
> @@
On 23.11.2010, at 20:51, anthony.per...@citrix.com wrote:
> From: Anthony PERARD
>
> With MapCache, we can handle a 64b target, even with a 32b host/qemu.
> So, we need to have target_phys_addr_t to 64bits.
>
> Signed-off-by: Anthony PERARD
> ---
> configure |3 +++
> 1 files changed, 3 in
On 29.11.2010, at 17:06, Anthony PERARD wrote:
> On Mon, 29 Nov 2010, Alexander Graf wrote:
>
>>
>> On 29.11.2010, at 16:10, Anthony PERARD wrote:
>>
>>> On Mon, 29 Nov 2010, Alexander Graf wrote:
>>>
On 23.11.2010, at 20:51, anthony.per...@citrix.com wrote:
> From: Antho
On 29.11.2010, at 18:49, Anthony Liguori wrote:
> On 11/29/2010 11:37 AM, Attila Sukosd wrote:
>>
>> Hi,
>>
>> I guess it should be abstract enough to support multiple back-ends, be it a
>> kernel driver or through libusb?
>
> Is this something that should just live in libusb?
>
> If what li
On 29.11.2010, at 18:42, Anthony Liguori wrote:
> Hi,
>
> 0.13 was a mess of a release (largely due to my lack of time) and I'd like to
> get us back onto a predictable schedule.
>
> Here's what I propose:
>
> 12/6 - fork off stable-0.14 tree; simultaneously release qemu-0.14.0-rc0
>
> For t
On Tue, Nov 23, 2010 at 06:53:44PM +, Peter Maydell wrote:
> Fix errors in the decoding of the Neon forms of fixed-point VCVT:
> * fixed-point VCVT is op 14 and 15, not 15 and 16
> * the fbits immediate field was being misinterpreted
> * the sense of the to_fixed bit was inverted
>
> Signed
On Tue, Nov 23, 2010 at 06:53:42PM +, Peter Maydell wrote:
> From: Adam Lackorzynski
>
> Refine check on bkpt so that smc and undefined instruction encodings are
> handled as an undefined instruction and trap.
>
> Signed-off-by: Adam Lackorzynski
> Signed-off-by: Peter Maydell
Reviewed-by
Am 29.11.2010 15:42, schrieb Anthony Liguori:
Does anyone know of a tool that convert texi to wiki syntax or know
enough about texi parsing that something could be rigged up?
Even if it takes a couple steps, like texi2xml, then xml->wiki, that
would be workable. I'm willing to do some leg wor
On Tue, Nov 23, 2010 at 06:53:40PM +, Peter Maydell wrote:
> From: Johan Bengtsson
>
> The PKHxx instructions were not recognized by the thumb2 decoder. The
> solution provided in this changeset is identical to the arm-mode
> implementation.
>
> Signed-off-by: Johan Bengtsson
> Signed-off-b
On Tue, Nov 23, 2010 at 06:53:49PM +, Peter Maydell wrote:
> The ARM architecture needs float/double to 16 bit integer conversions.
> (The 32 bit versions aren't sufficient because of the requirement
> to saturate at 16 bit MAXINT/MININT and to get the exception bits right.)
>
> Signed-off-by:
On Tue, Nov 23, 2010 at 06:53:50PM +, Peter Maydell wrote:
> Use the softfloat conversion routines for conversion to 16 bit
> integers, because just casting to a 16 bit type truncates the
> value rather than saturating it at 16-bit MAXINT/MININT.
>
> Signed-off-by: Peter Maydell
Reviewed-by:
On Mon, 29 Nov 2010, Alexander Graf wrote:
>
> On 23.11.2010, at 20:51, anthony.per...@citrix.com wrote:
>
> > From: Anthony PERARD
> >
> > With MapCache, we can handle a 64b target, even with a 32b host/qemu.
> > So, we need to have target_phys_addr_t to 64bits.
> >
> > Signed-off-by: Anthony PE
On Mon, 29 Nov 2010, Alexander Graf wrote:
>
> On 29.11.2010, at 17:06, Anthony PERARD wrote:
>
> > On Mon, 29 Nov 2010, Alexander Graf wrote:
> >
> >>
> >> On 29.11.2010, at 16:10, Anthony PERARD wrote:
> >>
> >>> On Mon, 29 Nov 2010, Alexander Graf wrote:
> >>>
>
> On 23.11.2010, at 20
On Wed, Nov 24, 2010 at 03:20:03PM +, Peter Maydell wrote:
> The padding in the target_ucontext_v2 is defined by the size of
> the target's sigset_t type, not the host's. (This bug only causes
> problems when we start using the uc_regspace[] array to expose
> VFP registers to userspace signal h
1 - 100 of 132 matches
Mail list logo
