Move USB HID request constants from hw/usb-hid.c to hw/usb.h
to allow other modules to use them.
Signed-off-by: Scott Tsai scottt...@gmail.com
---
hw/usb-hid.c | 20 ++--
hw/usb.h |8
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/hw/usb-hid.c
On 11/09/2009 09:35 PM, Jamie Lokier wrote:
What I'd like to know is, if all of QEMU's state is appropriately
recreated in the child instance, and KVM's device is reopened with a
copy of the kvm state (by using the recently introduced ioctls to get
and set it), will it fork the _guest RAM_
On 11/09/2009 08:41 PM, Glauber Costa wrote:
pc.c:
} else {
/* High and recent kernel */
real_addr= 0x1;
cmdline_addr = 0x2;
prot_addr= 0x10;
}
If I'm not totally mistaken, 0x1 is 1MB :-).
So yes, I think there should be
On 10.11.2009, at 14:02, Avi Kivity wrote:
On 11/09/2009 08:41 PM, Glauber Costa wrote:
pc.c:
} else {
/* High and recent kernel */
real_addr= 0x1;
cmdline_addr = 0x2;
prot_addr= 0x10;
}
If I'm not totally mistaken, 0x1 is
On 11/10/2009 03:03 PM, Alexander Graf wrote:
Anywhere you put it the bios has a right to trample. Of course our
bios (and its maintainer) are cooperative, but there's not reason to
impose on that if we can do the right thing and load the data at the
right moment.
Right. The only thing
On 10.11.2009, at 14:07, Avi Kivity wrote:
On 11/10/2009 03:03 PM, Alexander Graf wrote:
Anywhere you put it the bios has a right to trample. Of course
our bios (and its maintainer) are cooperative, but there's not
reason to impose on that if we can do the right thing and load the
data
Anthony Liguori wrote:
Jamie Lokier wrote:
Adam Litke wrote:
+s-stats.pswapin = has_feature(dev,
VIRTIO_BALLOON_F_RPT_SWAP_OUT) ?
+ dev-stats.pswapin : -1;
(etc.)
Why not simply have the guest fill in the unused fields with -1,
Avi Kivity wrote:
On 11/09/2009 09:35 PM, Jamie Lokier wrote:
What I'd like to know is, if all of QEMU's state is appropriately
recreated in the child instance, and KVM's device is reopened with a
copy of the kvm state (by using the recently introduced ioctls to get
and set it), will it
No question, this is a gdb issue. But, as it was confirmed in several
discusssions with gdb people, it is a non-trivial thing to fix. So until
qemu finds a gdb version attach with a rework x86 support, we have to
work around it by switching the register layout as the guest switches
its
Rusty Russell wrote:
On Tue, 10 Nov 2009 03:02:06 am Adam Litke wrote:
A simpler approach is to collect memory statistics in the virtio
balloon driver and communicate them to the host via the device config space.
There are two issues I see with this. First, there's an atomicity
On 11/10/2009 04:36 PM, Anthony Liguori wrote:
A stats vq might solve this more cleanly?
actual and target are both really just stats. Had we implemented
those with a vq, I'd be inclined to agree with you but since they're
implemented in the config space, it seems natural to extend the
On 11/10/2009 11:37 AM, Scott Tsai wrote:
Emulate the Vernier Go!Temp USB thermometer
(see: http://www.vernier.com/go/gotemp.html)
used in Greg Kroah-Hartman's Write a Real, Working, Linux Driver talk.
The emulation is complete enough for gregkh's sample driver and
using the vendor supplied SDK
On Wednesday 30 September 2009, Aurelien Jarno wrote:
Currently zero extensions ops are implemented by a and op with a
constant. This is then catched in some backend, and replaced by
a zero extension instruction. While this works well on RISC
machines, this adds a useless register move on
Avi Kivity wrote:
On 11/10/2009 04:36 PM, Anthony Liguori wrote:
A stats vq might solve this more cleanly?
actual and target are both really just stats. Had we implemented
those with a vq, I'd be inclined to agree with you but since they're
implemented in the config space, it seems
+ s-temperature++;
You're going to overheat very quickly.
Apart from making the driver work, is this actually useful?
I wanted the temperature to change with time to give a sense of
something is happening ^_^
The main user I had in mind was someone new to USB and Linux driver development
+ s-temperature++;
You're going to overheat very quickly.
Apart from making the driver work, is this actually useful?
I wanted the temperature to change with time to give a sense of
something is happening ^_^
The main user I had in mind was someone new to USB and Linux driver
development
On Fri, Oct 30, 2009 at 09:21:12PM +0900, Isaku Yamahata wrote:
Since It can be retrieved from pci configuration space,
the member is unnecessary.
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
Acked-by: Michael S. Tsirkin m...@redhat.com
---
hw/pci.c | 21 ++---
On Tue, Nov 10, 2009 at 02:51:21PM +, Paul Brook wrote:
On Wednesday 30 September 2009, Aurelien Jarno wrote:
Currently zero extensions ops are implemented by a and op with a
constant. This is then catched in some backend, and replaced by
a zero extension instruction. While this works
Scott Tsai scottt...@gmail.com wrote:
+ s-temperature++;
You're going to overheat very quickly.
Apart from making the driver work, is this actually useful?
I wanted the temperature to change with time to give a sense of
something is happening ^_^
The main user I had in mind was someone
On Thursday 08 October 2009, Mark McLoughlin wrote:
Hi,
Here's a series of patches which gets the ball rolling on adding
a -netdev option.
...
The idea is to de-emphasise the vlan support, and instead make
a nic directly connected to a host backend the default and recommended
On Fri, Oct 30, 2009 at 09:21:02PM +0900, Isaku Yamahata wrote:
use pci_set_word() for pci command register.
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
Acked-by: Michael S. Tsirkin m...@redhat.com
I thought I acked this already. It's an obvious one.
---
hw/pci.c |4 ++--
1
On Tue, 2009-11-10 at 15:44 +, Paul Brook wrote:
On Thursday 08 October 2009, Mark McLoughlin wrote:
Hi,
Here's a series of patches which gets the ball rolling on adding
a -netdev option.
...
The idea is to de-emphasise the vlan support, and instead make
a nic
On Sun, Nov 08, 2009 at 12:50:21PM +0200, Blue Swirl wrote:
Both mmu_init() and mvp_init() allocate structures, so call cpu_mips_register
only when creating a CPU.
In addition, maybe some of the some of the field initialization stuff
in cpu_mips_register, mmu_init, mvp_init, fpu_init etc.
On Tue, Nov 10, 2009 at 05:33:22PM +0200, Michael S. Tsirkin wrote:
On Fri, Oct 30, 2009 at 09:21:12PM +0900, Isaku Yamahata wrote:
Since It can be retrieved from pci configuration space,
the member is unnecessary.
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
Acked-by: Michael
On Fri, Oct 30, 2009 at 09:21:13PM +0900, Isaku Yamahata wrote:
This patch sorts out/enhances pci code to track pci bus topology
more accurately.
- Track host bus bridge with pci domain number. Although the
current qemu implementation supports only pci domian 0 yet.
- Track pci bridge
On Tue, Nov 10, 2009 at 11:33 PM, Alexander Graf ag...@suse.de wrote:
How about having a monitor command to change the temperature, leveraging a
common interface?
That way in the future real host temperature measurements could maybe get
forwarded there too. At least for battery I've had
On Tue, Nov 10, 2009 at 11:39 PM, Juan Quintela quint...@redhat.com wrote:
Change them in the middle of one interval?
once then arrived same limit, 40° or so go back to 20°?
I can do this.
On Monday 12 October 2009, Toni wrote:
Hi guys,
I found a solution for the problems with the fork and the exec under qemu
user-mode.
With the fork I enabled the NPTL and now it seems to work fine.
For the exec the problem was that it was execute natively, and so the qemu
process was killed
On Fri, Oct 30, 2009 at 09:21:14PM +0900, Isaku Yamahata wrote:
factor out the logic which converts io port address into pci device
and offset in PCI configuration space.
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
---
hw/pci.c | 32 ++--
1 files
On Fri, Oct 30, 2009 at 09:21:16PM +0900, Isaku Yamahata wrote:
change the first argument, void *opaque to PCIBus *s
of the pci_data_{read, write}.
They aren't used as direct callback so the argument type
don't have to be void*. So change it to the right type.
Signed-off-by: Isaku Yamahata
On Fri, Oct 30, 2009 at 09:21:20PM +0900, Isaku Yamahata wrote:
clean up pci_default_write_config() by the range helper functions.
Suggested by Michael S. Tsirkin m...@redhat.com
Cc: Michael S. Tsirkin m...@redhat.com
Signed-off-by: Isaku Yamahata yamah...@valinux.co.jp
Mabe you can float
On Mon, Nov 09, 2009 at 06:55:23PM +0200, Ulrich Hecht wrote:
On Monday 02 November 2009, Laurent Desnogues wrote:
That indeed looks strange: fixing the TB chaining on ARM
made nbench i386 three times faster. Note the gain was
less for FP parts of the benchmark due to the use of
On Fri, Oct 30, 2009 at 09:21:21PM +0900, Isaku Yamahata wrote:
When updated ROM expantion address of header type 0, it missed
to update mappings.
Add PCI_ROM_ADDRESS check whether to call pci_update_mappings()
Also update pci mapping when PCI_ROM_ADDRESS1 is written for header type 1.
On Mon, Nov 09, 2009 at 06:54:28PM +0200, Ulrich Hecht wrote:
On Monday 02 November 2009, Aurelien Jarno wrote:
First of all I have a question about s390/s390x. It seems that you
plan to support both s390 and s390x in the same file. Is that correct?
Actually, I didn't think about
On Tue, 10 Nov 2009 23:55:10 +0800
Scott Tsai scottt...@gmail.com wrote:
On Tue, Nov 10, 2009 at 11:33 PM, Alexander Graf ag...@suse.de wrote:
How about having a monitor command to change the temperature, leveraging a
common interface?
That way in the future real host temperature
On Tue, 2009-11-10 at 18:03 +0100, Juan Quintela wrote:
Mark McLoughlin mar...@redhat.com wrote:
On Fri, 2009-11-06 at 15:58 +0100, Juan Quintela wrote:
commit b04c4134d6de28c249277de19e523bfbe4aebbd6
broke incoming migration. After talking with Gleb, code was intended
to be the way is
Hi list,
For quite some time the PPC64 target (-M mac99 -cpu 970fx) is broken
in early init code:
6OF: ** translation for device /p...@f200/p...@d/mac...@10/
interrupt-control...@4 **
6OF: bus is default (na=1, ns=1) on /p...@f200/p...@d/mac...@10
4OF: translating address:
Mark McLoughlin mar...@redhat.com wrote:
On Tue, 2009-11-10 at 18:03 +0100, Juan Quintela wrote:
Mark McLoughlin mar...@redhat.com wrote:
On Fri, 2009-11-06 at 15:58 +0100, Juan Quintela wrote:
commit b04c4134d6de28c249277de19e523bfbe4aebbd6
broke incoming migration. After talking with
On Tue, Nov 10, 2009 at 8:04 PM, Alexander Graf ag...@suse.de wrote:
Hi list,
For quite some time the PPC64 target (-M mac99 -cpu 970fx) is broken in
early init code:
6OF: ** translation for device
/p...@f200/p...@d/mac...@10/interrupt-control...@4 **
6OF: bus is default (na=1,
On Wed, 11 Nov 2009 01:52:12 +0800
Scott Tsai scottt...@gmail.com wrote:
On Wed, Nov 11, 2009 at 1:06 AM, Luiz Capitulino lcapitul...@redhat.com
wrote:
I'd certainly like to make this code useful for something other than
developer training.
How about a new monitor command
According to SCSI-2 specification,
http://ldkelley.com/SCSI2/SCSI2/SCSI2/SCSI2-08.html#8.2.5 ,
if the allocation length of the command descriptor block (CDB) is too
small to transfer all of the parameters, the additional length shall
not be adjusted to reflect the truncation.
The 36 mandatory
On Tue, Nov 10, 2009 at 10:50 PM, Aurelien Jarno aurel...@aurel32.net wrote:
Please note that at least qemu-system-arm, qemu-system-mips and
qemu-system-mipsel are broken by this commit:
Given that none of the devices touched by the commit should be used by
these targets, the breakage comes
On Tue, Nov 10, 2009 at 11:19:40PM +0200, Blue Swirl wrote:
On Tue, Nov 10, 2009 at 10:50 PM, Aurelien Jarno aurel...@aurel32.net wrote:
Please note that at least qemu-system-arm, qemu-system-mips and
qemu-system-mipsel are broken by this commit:
Given that none of the devices touched by
Rusty Russell wrote:
On Tue, 10 Nov 2009 03:02:06 am Adam Litke wrote:
A simpler approach is to collect memory statistics in the virtio
balloon driver and communicate them to the host via the device config space.
There are two issues I see with this. First, there's an atomicity
Some of the generated tcg code is not very optimal, for example a
single vld4.8 instruction can generate over 250 tcg ops. I did some
optimizations and got it under 200 but do you think it could be an
issue that a single instruction can expand to so many tcg ops? I mean
besides the fact
On the code itself, I don't really like the remaining, new_tmp(),
dead_tmp(), and even more the fact that some functions can allocate
(e.g load_reg) or free (e.g. store_reg) some TCG variables implicitely.
This is a way to make errors by reallocating or forgetting to free some
variables,
On Tue, Nov 10, 2009 at 11:38:49PM +, Paul Brook wrote:
Some of the generated tcg code is not very optimal, for example a
single vld4.8 instruction can generate over 250 tcg ops. I did some
optimizations and got it under 200 but do you think it could be an
issue that a single
On Wed, 11 Nov 2009 01:06:14 am Anthony Liguori wrote:
Rusty Russell wrote:
On Tue, 10 Nov 2009 03:02:06 am Adam Litke wrote:
A simpler approach is to collect memory statistics in the virtio
balloon driver and communicate them to the host via the device config
space.
Rusty Russell wrote:
On Wed, 11 Nov 2009 08:22:42 am Anthony Liguori wrote:
Rusty Russell wrote:
On Tue, 10 Nov 2009 03:02:06 am Adam Litke wrote:
A simpler approach is to collect memory statistics in the virtio
balloon driver and communicate them to the host via the device
Scott Tsai wrote:
On Wed, Nov 11, 2009 at 1:06 AM, Luiz Capitulino lcapitul...@redhat.com wrote:
I'd certainly like to make this code useful for something other than
developer training.
How about a new monitor command thermometer_set that works like mouse_move?
thermometer_set would just set
I reworked the second patch in this series to add generic monitor commands
to change the temperature reported from thermometers.
Thermometer devices can now include sensor.h and call
'qemu_add_therm_temp_handler'
to register themselves.
I went with separate 'therm_set DEVICE_INDEX' and
Move USB HID request constants from hw/usb-hid.c to hw/usb.h
to allow other modules to use them.
Signed-off-by: Scott Tsai scottt...@gmail.com
---
hw/usb-hid.c | 20 ++--
hw/usb.h |8
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/hw/usb-hid.c
Emulate the Vernier Go!Temp USB thermometer
(see: http://www.vernier.com/go/gotemp.html)
used in Greg Kroah-Hartman's Write a Real, Working, Linux Driver talk.
The emulation is complete enough for gregkh's sample driver and
using the vendor supplied SDK through the in-kernel 'ldusb' module under
Adds documentation for the '-usbdevice thermometer' option.
Signed-off-by: Scott Tsai scottt...@gmail.com
---
qemu-options.hx |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index b65fd74..c2e3b6c 100644
--- a/qemu-options.hx
+++
On Thursday 22 October 2009, Aurelien Jarno wrote:
On Wed, Oct 21, 2009 at 03:52:22PM +0200, Ulrich Hecht wrote:
sync allows concurrent accesses to locations in memory through different
TCG variables. This comes in handy when you are emulating CPU registers
that can be used as either 32 or
On Wed, Nov 11, 2009 at 8:57 AM, Greg KH gre...@suse.de wrote:
What code? Where is it at?
http://patchwork.ozlabs.org/patch/38118/
This code emulates a Vernier Go!Temp device in qemu.
I wrote this to enable people to follow your driver tutorial without
buying the gadget.
(I implemented
I immediately reproduced the problem locally. It turns out that
kvm reflects packets coming from one guest NIC on another guest
NIC, and since both are connected to the same bridge we're getting
endless packet storm. To a level when kvm process becomes 100%
busy and does not respond to
On Monday 26 October 2009, Michael S. Tsirkin wrote:
wmb must be at least a compiler barrier, even without SMP.
Why?
Paul
Mark McLoughlin wrote:
On Fri, 2009-10-23 at 20:25 +0400, Michael Tokarev wrote:
I've two questions:
o what's the intended usage of all-vlan-equal case, when kvm (or qemu)
reflects packets from one interface to another? It's what bridge
in linux is for, I think.
I don't think
But I certainly do _not_ want to update the SCSI disk
emulation, as this is really quite tied to the SCSI parallel
interface used by the old lsi53c895a.c.
This is completely untrue. scsi-disk.c contains no transport-specific code. It
is deliberately designed to be independent of both the
On Wed, Nov 11, 2009 at 8:09 AM, Anthony Liguori anth...@codemonkey.ws wrote:
That said, if we position this as an example device, I think that makes
sense. But that suggests that we should document the heck out of it and
make it a learning experience for QEMU too. It could be an example of
On Wed, 11 Nov 2009 10:37:56 am Anthony Liguori wrote:
Rusty Russell wrote:
You register an outbuf at initialization time. The host hands it back when
it wants you to refill it with stats.
That's strangely backwards. Guest send a stat buffer that's filled out,
host acks it when it
On Wednesday 11 November 2009, Scott Tsai wrote:
I reworked the second patch in this series to add generic monitor commands
to change the temperature reported from thermometers.
Thermometer devices can now include sensor.h and call
'qemu_add_therm_temp_handler' to register themselves.
This
(this is mostly to get some ideas going rather than trying to get anything
upstream... yet!)
This version of tcg_out_mov for i386's tcg-target.c filters out the
mov %ebx, %edx
mov %ebx, [some index]
mov %edx, %ebx
I don't have benchmarks, but it does remove a few mov's and qemu can still
load
64 matches
Mail list logo
