On 10/18/10 21:36, Stefan Weil wrote:
There is already some kind of error feedback: the rom will not work.
For etherboot roms, booting from network won't work.
VGA works, after hacking the vgabios to not have the PCI ID hardcoded
elsewhere.
Nevertheless /me gets the feeling that we better sh
[PATCH 2/2] Add documentation for QMP commands:
- query-trace
- query-trace-events
- query-trace-file.
Signed-off-by: Prerna Saxena
---
qmp-commands.hx | 94 +++
1 files changed, 94 insertions(+), 0 deletions(-)
diff --git a/qmp-commands
[PATCH 1/2] Introduce QMP interfaces :
- query-trace
- query-trace-events
- query-trace-file
Signed-off-by: Prerna Saxena
---
monitor.c | 53 ---
simpletrace.c | 69 +
simpletrace.h |5
This patch set introduces three QMP query interfaces for tracing :
* query-trace: to list current contents of trace-buffer
* query-trace-events : to list all available trace-events with their
state.
* query-trace-file : to list currently set trace-file with its st
Am 19.10.2010 um 02:10 schrieb Anthony Liguori :
> On 10/18/2010 06:29 PM, Alexander Graf wrote:
>>> A user will get a really nasty surprise if they think they can use a flag
>>> or rely on QEMU to prevent a VM from doing something nasty with a device.
>>> If they have this feeling of security
On 10/18/2010 07:51 PM, Luiz Capitulino wrote:
On Mon, 18 Oct 2010 11:36:55 +0530
Prerna Saxena wrote:
This patch set introduces two QMP interfaces for tracing :
* query-trace: to list current contents of trace-buffer
* query-trace-events : to list all available trace-events with thei
* Juan Quintela (quint...@redhat.com) wrote:
>
> Please send in any agenda items you are interested in covering.
- 0.13.X -stable handoff
- 0.14 planning
- threadlet work
- virtfs proposals
There is no reason why SRAO event received by the main thread
is the only one that being broadcasted.
According to the x86 ASDM vol.3A 15.10.4.1,
MCE signal is broadcast on processor version 06H_EH or later.
This change is required to handle SRAR in smp guests.
Signed-off-by: Hidetoshi Seto
---
And restruct this block to call kvm_mce_in_exception() only when it is
required.
Signed-off-by: Hidetoshi Seto
---
target-i386/kvm.c | 16 ++--
1 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index d940175..98a0505 100644
--- a/
(2010/10/15 22:30), Marcelo Tosatti wrote:
> On Fri, Oct 15, 2010 at 10:52:05AM +0900, Hidetoshi Seto wrote:
>> (2010/10/15 10:06), Marcelo Tosatti wrote:
>>> On Thu, Oct 14, 2010 at 05:55:28PM +0900, Jin Dongming wrote:
There is no reason why SRAO event received by the main thread
is the
On Mon, Oct 18, 2010 at 11:47:42AM +0200, Michael S. Tsirkin wrote:
> On Mon, Oct 18, 2010 at 06:34:21PM +0900, Isaku Yamahata wrote:
> > This patch set fixes PCI bar allocation when bar overflow occured.
> > I checked if pmm_alloc facility can be used, but it doesn't suit for
> > pci bar allocatio
On Mon, Oct 18, 2010 at 11:55:08AM +0200, Michael S. Tsirkin wrote:
> > +static u32 pci_region_alloc_align(struct pci_region *r, u32 size, u32
> > align)
> > +{
> > +if (r->cur_end == PCI_REGION_DISABLED) {
> > +return 0;
> > +}
>
> So is special value PCI_REGION_DISABLED or cur_e
An additional note is that,
qemu-img snapshot -l
shows VM_Size = 0
Has anyone observed this issue before?
Regards
--
On Tue, Oct 19, 2010 at 9:18 AM, Ubuntu Explorer
wrote:
> I also read the following
>
> VM snapshots currently have the following known limitations:
> They cannot cope with re
I also read the following
VM snapshots currently have the following known limitations:
They cannot cope with removable devices if they are removed or inserted
after a snapshot is done.
A few device drivers still have incomplete snapshot support so their state
is not saved or restored properly (in
On 10/18/2010 06:29 PM, Alexander Graf wrote:
A user will get a really nasty surprise if they think they can use a flag or
rely on QEMU to prevent a VM from doing something nasty with a device. If they
have this feeling of security, they're likely to chmod the device to allow
unprivileged use
Thanks for your help.
But, after commenting out snapshot option, I still cannot save the VM state
into the ide0-hd0 block device.
Here is some more information about the problem.
I am trying to do the following
a. info block
shows virtio, ide0-hd0
b. savevm snapshot_name
c. info snapshots
On 30.08.2009, at 02:14, Anthony Liguori wrote:
> Carl-Daniel Hailfinger wrote:
>> The guest can also mess up other devices with the help of specially
>> crafted firmware. So even if the user does not care about the effects on
>> a particular device, a firmware upgrade might affect other devices
Block hot unplug is racy since the guest is required to acknowlege the ACPI
unplug event; this may not happen synchronously with the device removal command
This series aims to close a gap where by mgmt applications that assume the
block resource has been removed without confirming that the guest h
This patch series decouples the detachment of a block device from the removal
of the backing pci-device. Removal of a hotplugged pci device requires the
guest to respond before qemu tears down the block device. In some cases, the
guest may not respond leaving the guest with continued access to the
Add a function to find a drive by id string.
Signed-off-by: Ryan Harper
---
blockdev.c | 12
blockdev.h |1 +
2 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/blockdev.c b/blockdev.c
index ff7602b..a00b3fa 100644
--- a/blockdev.c
+++ b/blockdev.c
@@ -75,6 +75,18
The following changes since commit 38cc9b607f85017b095793cab6c129bc9844f441:
Jindrich Makovicka (1):
issue snd_pcm_start() when capturing audio
are available in the git repository at:
git://repo.or.cz/qemu/aliguori/jvrao.git for-anthony
Aneesh Kumar K.V (2):
virtio-9p: Use laye
On 10/14/2010 05:57 AM, Anthony Liguori wrote:
>
> I've always been sceptical of this. When physical systems have a large
> number of NICs, it's via multiple functions, not a bunch of PCI bridges.
>
Actually a lot of multiport PCI cards are in fact single or dual NICs
behind PCI bridges.
On 10/18/2010 02:36 PM, Stefan Weil wrote:
Maybe a more perfect solution would only patch the preconfigured
rom files but not user configured files, but I don't think we
need this degree of perfection.
Generally speaking, patching third-party code is not something that we
should get in the hab
On 10/18/2010 02:03 PM, Michael S. Tsirkin wrote:
On Mon, Oct 18, 2010 at 01:42:06PM -0500, Anthony Liguori wrote:
+/* Patch the PCI vendor and device ids in a PCI rom image if necessary.
+ This is needed for an option rom which is used for more than one device. */
+static void pci_patch_i
Am 18.10.2010 21:03, schrieb Michael S. Tsirkin:
On Mon, Oct 18, 2010 at 01:42:06PM -0500, Anthony Liguori wrote:
+/* Patch the PCI vendor and device ids in a PCI rom image if
necessary.
+ This is needed for an option rom which is used for more than one
device. */
+static void pci_patch_ids(PC
Am 18.10.2010 20:53, schrieb Anthony Liguori:
On 10/18/2010 01:44 PM, Anthony Liguori wrote:
On 10/18/2010 12:55 PM, Stefan Weil wrote:
PCI devices with different vendor or device ids sometimes share
the same rom code. Only the ids and the checksum
differs in a boot rom for such devices.
The i
On Mon, Oct 18, 2010 at 01:42:06PM -0500, Anthony Liguori wrote:
> >>+/* Patch the PCI vendor and device ids in a PCI rom image if necessary.
> >>+ This is needed for an option rom which is used for more than one
> >>device. */
> >>+static void pci_patch_ids(PCIDevice *pdev, uint8_t *ptr, int si
On 10/18/2010 12:30 PM, Oleg Sadov wrote:
I don't understand reasons for such locale-default keyboard settings for
qemu too, but may be it's useful for someone...
-k only exists to deal with crappy VNC clients.
If you use a good VNC client (like vinagre or virt-viewer) then you
don't have
On 10/18/2010 01:44 PM, Anthony Liguori wrote:
On 10/18/2010 12:55 PM, Stefan Weil wrote:
PCI devices with different vendor or device ids sometimes share
the same rom code. Only the ids and the checksum
differs in a boot rom for such devices.
The i825xx ethernet controller family is a typical e
Am 18.10.2010 20:32, Scott Wood wrote:
> On Mon, Oct 04, 2010 at 04:15:58PM -0500, Scott Wood wrote:
>> This will deadlock when the I/O thread is used, since the
>> CPU thread is blocked waiting for qemu_system_ready.
>>
>> The synchronization is unnecessary since this is before
>> cpu_synchronize_
On 10/18/2010 12:55 PM, Stefan Weil wrote:
PCI devices with different vendor or device ids sometimes share
the same rom code. Only the ids and the checksum
differs in a boot rom for such devices.
The i825xx ethernet controller family is a typical example
which is implemented in hw/eepro100.c. It
On 10/18/2010 12:58 PM, Michael S. Tsirkin wrote:
On Mon, Oct 18, 2010 at 07:55:11PM +0200, Stefan Weil wrote:
PCI devices with different vendor or device ids sometimes share
the same rom code. Only the ids and the checksum
differs in a boot rom for such devices.
The i825xx ethernet control
On 10/18/2010 05:09 AM, Gerd Hoffmann wrote:
On 10/15/10 23:05, Anthony Liguori wrote:
On 10/15/2010 03:51 PM, Stefan Weil wrote:
PCI device with different device ids sometimes share
the same rom code. Only the device id and the checksum
differ in a boot rom for such devices.
BTW, SeaBIOS doe
On 10/18/2010 03:22 AM, Roedel, Joerg wrote:
(Sorry for the late reply)
On Thu, Oct 07, 2010 at 08:48:06AM -0400, Anthony Liguori wrote:
On 10/07/2010 03:42 AM, Roedel, Joerg wrote:
On Wed, Oct 06, 2010 at 03:24:59PM -0400, Anthony Liguori wrote:
+qemu_compat_version =
On Mon, Oct 04, 2010 at 04:15:58PM -0500, Scott Wood wrote:
> This will deadlock when the I/O thread is used, since the
> CPU thread is blocked waiting for qemu_system_ready.
>
> The synchronization is unnecessary since this is before
> cpu_synchronize_all_post_init().
>
> Signed-off-by: Scott Wo
Signed-off-by: Venkateswararao Jujjuri
---
hw/virtio-9p.c | 17 +
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/hw/virtio-9p.c b/hw/virtio-9p.c
index 3b2d49c..9575698 100644
--- a/hw/virtio-9p.c
+++ b/hw/virtio-9p.c
@@ -325,6 +325,14 @@ static int number_to_str
On Mon, Oct 18, 2010 at 07:55:11PM +0200, Stefan Weil wrote:
> PCI devices with different vendor or device ids sometimes share
> the same rom code. Only the ids and the checksum
> differs in a boot rom for such devices.
>
> The i825xx ethernet controller family is a typical example
> which is impl
PCI devices with different vendor or device ids sometimes share
the same rom code. Only the ids and the checksum
differs in a boot rom for such devices.
The i825xx ethernet controller family is a typical example
which is implemented in hw/eepro100.c. It uses at least
3 different device ids, so nor
Am 18.10.2010 17:50, schrieb Gerd Hoffmann:
On 10/18/10 15:30, Gerd Hoffmann wrote:
Hi,
When following this argumentation the vendor id sanity check shouldn't
be there in the first place ;)
The sanity check is simply there because I had no test case
which patches the vendor id. How could I
The QEMU team is pleased to announce the availability of the 0.13.0 release.
This release consists of over 2,500 commits from 145 contributors.
Some major features were added in this release including:
- vhost-net: kernel-accelerating network backend for virtio devices
(using KVM)
- qmp: si
Sorry for delay with answer -- vacations time without e-mail account
access.
07/10/2010 08:38 +0400, Michael Tokarev wrote:
> 06.10.2010 23:56, Eduardo Habkost wrote:
> >
> > Anybody using a russian keyboard layout who can test this change and
> > confirm it works as expected?
>
> I can perform
On Mon, Oct 18, 2010 at 05:48:16PM +0200, Juan Quintela wrote:
> Gleb Natapov wrote:
> > Add save/restore of MSR for migration and cpuid bit.
>
> It is there a way to test if async page faults are in use?
> if so, we can add a subsection instead of changing the cpuversion.
>
Yeah. Good idea. For
The L1 table grow operation includes a size calculation that bumps up
the new L1 table size in order to anticipate the size needs of vmstate
data. This helps reduce the number of times that the L1 table has to be
grown when vmstate data is appended.
This size overhead is not necessary during imag
On 10/18/2010 05:48 PM, Juan Quintela wrote:
Gleb Natapov wrote:
> Add save/restore of MSR for migration and cpuid bit.
It is there a way to test if async page faults are in use?
Yes, msr != 0 -> need a subsection. Good idea.
if so, we can add a subsection instead of changing the cpuvers
On 10/18/10 15:30, Gerd Hoffmann wrote:
Hi,
When following this argumentation the vendor id sanity check shouldn't
be there in the first place ;)
The sanity check is simply there because I had no test case
which patches the vendor id. How could I test with vga bios?
No trivial way as the
Gleb Natapov wrote:
> Add save/restore of MSR for migration and cpuid bit.
It is there a way to test if async page faults are in use?
if so, we can add a subsection instead of changing the cpuversion.
I think that at some point we are going to need a bitmap that indicates
what MSR's have been us
Please send in any agenda items you are interested in covering.
thanks,
Juan.
Hi,I also investigate to implement trace target memory. Now i can trace logical address ( simulate ARM on i386) I focus on tcg_out_qemu_ld and tcg_out_qemu_st function to generate i386 code. But i found that , QEMU don't generate full memory access for loop ( it only generate for 1 TB on loop )How
On Mon, 18 Oct 2010 11:36:55 +0530
Prerna Saxena wrote:
> This patch set introduces two QMP interfaces for tracing :
>
> * query-trace: to list current contents of trace-buffer
> * query-trace-events : to list all available trace-events with their state.
This is in my to-review queue, b
On Sat, 16 Oct 2010 19:42:43 +0200
Jan Kiszka wrote:
> Am 16.10.2010 18:28, Blue Swirl wrote:
> > On Sat, Oct 16, 2010 at 12:37 AM, Paolo Bonzini wrote:
> >> On 10/15/2010 07:41 PM, Blue Swirl wrote:
> >>>
> >>> Which functions are optimized away and which aren't?
> >>
> >> It's builtins only th
On Thu, 14 Oct 2010 09:51:02 +0900
Hidetoshi Seto wrote:
> Fix example of STOP event that was just copy-and-pasted.
>
> Signed-off-by: Hidetoshi Seto
Applied to the QMP queue, thanks.
> ---
> QMP/qmp-events.txt |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/Q
This introduces a new tracing backend that targets the SystemTAP
implementation of DTrace userspace tracing. The core functionality
should be applicable and standard across any DTrace implementation
on Solaris, OS-X, *BSD, but the Makefile rules will likely need
some small additional changes to cop
Hi,
When following this argumentation the vendor id sanity check shouldn't
be there in the first place ;)
The sanity check is simply there because I had no test case
which patches the vendor id. How could I test with vga bios?
No trivial way as the vgabios needs to be patched to handle tha
Add save/restore of MSR for migration and cpuid bit.
Signed-off-by: Gleb Natapov
diff --git a/qemu-kvm-x86.c b/qemu-kvm-x86.c
index bb09fd8..5d8c428 100644
--- a/qemu-kvm-x86.c
+++ b/qemu-kvm-x86.c
@@ -678,6 +678,9 @@ static int get_msr_entry(struct kvm_msr_entry *entry,
CPUState *env)
Signed-off-by: Alon Levy
---
Makefile.objs |2 +-
configure | 20 ++
hw/ccid-card-emulated.c | 497 +++
hw/ccid-card-passthru.c |6 -
hw/usb-ccid.c |2 +
5 files changed, 520 insertions(+), 7 deletions(-)
Meant to be applied after the usb-ccid v3 patch on the list.
Causes --enable-smartcard to depend on libcac_card, library for emulating
CAC compliant smart cards at http://cgit.freedesktop.org/~alon/cac_card/
hw/ccid-card-emulated.c: new device
Makefile.objs: add ccid-card-emulated.o if --enable-sm
Hi,
Am 18.10.2010 13:54, schrieb Gerd Hoffmann:
Hi,
As far as I know there is no well-defined checksum offset.
The checksum is simply set by modifying any byte (which
normally should be unused).
Etherboot has some unused bytes at the beginning of rom data
and always uses the same offset 6.
I forgot to add the [qemu-iotests] tag, sorry. This applies to
Christoph's qemu-iotests suite at:
http://git.kernel.org/?p=linux/kernel/git/hch/qemu-iotests.git;a=summary
Stefan
Note that 019 current fails for both qcow2 and qed due to an outdated
.out file.
Signed-off-by: Stefan Hajnoczi
---
017 |2 +-
018 |2 +-
019 |2 +-
020 |2 +-
024 |4 ++--
027 |2 +-
028 |2 +-
common|6 ++
common
Brad Jorsch writes (
http://bugs.debian.org/578846 ):
The USB keyboard emulation's translation table in hw/usb-hid.c doesn't
match the codes actually sent for the Logo (a.k.a. "Windows") or Menu
keys. This results in the guest OS not being able to receive these keys
at all when the USB k
On 10/18/2010 06:34 AM, Michael Tokarev wrote:
Can we fix this trivial bug please?
See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578846
https://bugs.launchpad.net/qemu/+bug/584139
I switched qemu-kvm in debian to use qemu-keymaps package
(separately packaged keymaps), but it re-intro
The translation of REVSH shifted the low byte 8 steps left before performing
an 8-bit sign extend, causing this part of the expression to alwas be 0.
The fix for this is either to extend before shifting or switch to a 16-bit
extend. I choose the former.
Signed-off-by: Johan Bengtsson
---
target-
On 10/17/2010 11:58 PM, Sergei Steshenko wrote:
Hello,
though there is already
http://download.savannah.gnu.org/releases/qemu/qemu-0.13.0.tar.gz
available, I don't see its changelog on
http://wiki.qemu.org/Index.html
.
Is it expected to be this way ?
I haven't sent the announce yet (wh
The regular expression to parse trace event definitions assumed the
format string would be a simple double-quoted string. However, we now
use PRI?64 for portability which splits string literals. The regular
expression can disregard the format string entirely since simpletrace.py
never needs to us
Document the restriction that format strings must begin and end with
double quotes. This is for easy parsing since we don't run cpp over
trace-events.
Signed-off-by: Stefan Hajnoczi
---
docs/tracing.txt |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/docs/tracing.tx
From: Blue Swirl
Replace debug printf statements with tracepoints.
Signed-off-by: Blue Swirl
Signed-off-by: Stefan Hajnoczi
---
hw/apic.c| 48 ++--
trace-events | 12
2 files changed, 30 insertions(+), 30 deletions(-)
diff --gi
Thanks for pointing out this problem with simpletrace.py. There are two
issues:
1. The regular expression used by simpletrace.py to parse trace event
declarations cannot cope with concatenated string literals.
2. Format strings must begin and end with double quotes. This was previously
und
On 10/18/2010 12:47 PM, Arun R Bharadwaj wrote:
* Avi Kivity [2010-10-17 10:57:23]:
> On 10/14/2010 11:32 PM, Venkateswararao Jujjuri (JV) wrote:
> >>
> >> Blocking is somewhat against the spirit of the thing, no? While I
agree that
> >> the current cancel API is hard to use correct
Hi,
As far as I know there is no well-defined checksum offset.
The checksum is simply set by modifying any byte (which
normally should be unused).
Etherboot has some unused bytes at the beginning of rom data
and always uses the same offset 6.
Ah, so you don't actually update the checksum bu
Can we fix this trivial bug please?
See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578846
https://bugs.launchpad.net/qemu/+bug/584139
I switched qemu-kvm in debian to use qemu-keymaps package
(separately packaged keymaps), but it re-introduces
debian#578846.
Thanks!
/mjt
Am 18.10.2010 12:04, schrieb Gerd Hoffmann:
Hi,
+/* Don't patch a rom with wrong vendor id (might be changed if
needed). */
+if (vendor_id != rom_vendor_id) {
+return;
+}
Yes, please drop that one. If this is accepted I'd like to use this for
vga roms too, so we have t
* Avi Kivity [2010-10-17 10:57:23]:
> On 10/14/2010 11:32 PM, Venkateswararao Jujjuri (JV) wrote:
> >>
> >> Blocking is somewhat against the spirit of the thing, no? While I agree
> >> that
> >> the current cancel API is hard to use correctly, blocking defeats the
> >> purpose of
> >> the
On Sun, Oct 17, 2010 at 01:50:33PM +, Blue Swirl wrote:
> Move timer init functions to a new file, qemu-timer-common.c. Make other
> critical timer functions inlined to preserve performance in
> qemu-timer.c, also move muldiv64() (used by the inline functions)
> to qemu-timer.h.
>
> Adjust blo
On Friday 15 October 2010, Michael S. Tsirkin wrote:
> On Thu, Oct 14, 2010 at 11:40:52PM +0200, Dragos Tatulea wrote:
> > Hi,
> >
> > I'm starting a thread related to the TODO item mentioned in the
> > subject. Currently still gathering info and trying to make kvm &
> > macvtap play nicely t
On Sun, Oct 17, 2010 at 08:05:45AM +, Blue Swirl wrote:
> Use PRI*64 to print full 64 bit data even on ILP32 hosts.
>
> Print also sixth tracepoint parameter.
>
> Cc: Stefan Hajnoczi
> Signed-off-by: Blue Swirl
> ---
> simpletrace.c |6 --
> 1 files changed, 4 insertions(+), 2 dele
On 10/15/10 23:05, Anthony Liguori wrote:
On 10/15/2010 03:51 PM, Stefan Weil wrote:
PCI device with different device ids sometimes share
the same rom code. Only the device id and the checksum
differ in a boot rom for such devices.
BTW, SeaBIOS doesn't reject ROMs when they're loaded via romba
Hi,
+/* Don't patch a rom with wrong vendor id (might be changed if needed). */
+if (vendor_id != rom_vendor_id) {
+return;
+}
Yes, please drop that one. If this is accepted I'd like to use this for
vga roms too, so we have to carry only two of them instead of four.
+
On Mon, Oct 18, 2010 at 06:34:22PM +0900, Isaku Yamahata wrote:
> This patch adds helper functions to manage pci area.
>
> Signed-off-by: Isaku Yamahata
> ---
> Makefile |3 +-
> src/pci_region.c | 70
> ++
> src/util.h |
On Mon, Oct 18, 2010 at 06:34:21PM +0900, Isaku Yamahata wrote:
> This patch set fixes PCI bar allocation when bar overflow occured.
> I checked if pmm_alloc facility can be used, but it doesn't suit for
> pci bar allocation. So I resulted in new API, pci_region which
> encapsulates region allocati
This patch adds helper functions to manage pci area.
Signed-off-by: Isaku Yamahata
---
Makefile |3 +-
src/pci_region.c | 70 ++
src/util.h | 15 +++
3 files changed, 87 insertions(+), 1 deletions(-)
create mode 1
This patch cleans up pci region allocation with pci_region.
Now it is aware of overflow.
Signed-off-by: Isaku Yamahata
---
src/pciinit.c | 122 -
1 files changed, 60 insertions(+), 62 deletions(-)
diff --git a/src/pciinit.c b/src/pciinit.
This patch set fixes PCI bar allocation when bar overflow occured.
I checked if pmm_alloc facility can be used, but it doesn't suit for
pci bar allocation. So I resulted in new API, pci_region which
encapsulates region allocation and overflow checks.
The first patch introduces pci_region, and the s
On 10/18/2010 10:15 AM, jes.soren...@redhat.com wrote:
From: Jes Sorensen
Hi,
Here is another set of patches which tries to split up osdep.c further
into posix and win32 versions. It introduces oslib-{posix,win32}.c
files which are used for functions that are OS specific core library
functional
From: Jes Sorensen
This consolidates the duplicated oom_check() functions, as well as
splitting them into OS dependant versions to avoid the #ifdef
grossness that was present in the old osdep.c version.
Signed-off-by: Jes Sorensen
---
Makefile.target |2 +-
oslib-posix.c |8 +++-
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
osdep.c| 31 ---
osdep.h| 15 ---
oslib-win32.c | 27 +++
posix-aio-compat.c |1 +
qemu-common.h |5 +
qemu-img.c |1
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
os-posix.c | 21 +
os-win32.c | 24
osdep.c| 38 --
3 files changed, 45 insertions(+), 38 deletions(-)
diff --git a/os-posix.c b/os-posix.c
index 612b64
(Sorry for the late reply)
On Thu, Oct 07, 2010 at 08:48:06AM -0400, Anthony Liguori wrote:
> On 10/07/2010 03:42 AM, Roedel, Joerg wrote:
> > On Wed, Oct 06, 2010 at 03:24:59PM -0400, Anthony Liguori wrote:
> >
> +qemu_compat_version = machine->compat_version;
> +
>
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
os-posix.c | 32
osdep.c| 34 --
2 files changed, 32 insertions(+), 34 deletions(-)
diff --git a/os-posix.c b/os-posix.c
index 6321e99..612b641 100644
--- a/os-posix.c
++
From: Jes Sorensen
TRUE/FALSE are generally reserved keywords and shouldn't be defined in
a driver like this. Rename the macros to SDP_TRUE and SDP_FALSE
respectively.
Signed-off-by: Jes Sorensen
---
hw/bt-sdp.c | 20 ++--
1 files changed, 10 insertions(+), 10 deletions(-)
d
From: Jes Sorensen
No need to include stdlib.h for BSD as it is included by
qemu-common.h, windows.h is handled by sysemu.h and osdep.c no longer
needs malloc.h
Signed-off-by: Jes Sorensen
---
osdep.c |8
1 files changed, 0 insertions(+), 8 deletions(-)
diff --git a/osdep.c b/osd
On 10/16/10 21:32, Blue Swirl wrote:
> On Sat, Oct 16, 2010 at 4:04 PM, wrote:
>> From: Jes Sorensen
>>
>> In addition add sysemu.h includes to file requiring a prototype for
>> ffs()
>
> There are probably a lot more files which would need that:
> /src/qemu/hw/sd.c: In function 'sd_normal_comm
From: Jes Sorensen
This moves library functions used by both QEMU and the QEMU tools,
such as qemu-img, qemu-nbd etc. from osdep.c to oslib-{posix,win32}.c
In addition it introduces oslib-obj.y to the Makefile set to be
included by the various targets, instead of relying on these library
functio
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
osdep.c | 22 --
oslib-posix.c | 22 ++
2 files changed, 22 insertions(+), 22 deletions(-)
diff --git a/osdep.c b/osdep.c
index 902fce9..926c8ad 100644
--- a/osdep.c
+++ b/osdep.c
@@ -235,28 +2
From: Jes Sorensen
Signed-off-by: Jes Sorensen
---
osdep.c | 38 --
oslib-posix.c | 15 +++
oslib-win32.c | 21 +
3 files changed, 36 insertions(+), 38 deletions(-)
diff --git a/osdep.c b/osdep.c
index 581768a..902
From: Jes Sorensen
Hi,
Here is another set of patches which tries to split up osdep.c further
into posix and win32 versions. It introduces oslib-{posix,win32}.c
files which are used for functions that are OS specific core library
functionality, like gettimeofday(), and which is used by both QEMU
** Changed in: linux (Gentoo Linux)
Status: Fix Released => Won't Fix
--
Hardy alpha [2-6] daily-live i386 don't boot
https://bugs.launchpad.net/bugs/181561
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in The Linux Kern
On Mon, Oct 18, 2010 at 09:08:09AM +0200, Michael S. Tsirkin wrote:
> > The spec says the lower bits are read-only and they have its meaning.
>
> Yes. but my question is why even touch io base/io limit at all
> in this function?
> It looks like guest can not rely on these being 0 after reset.
Oh
On Mon, Oct 18, 2010 at 04:17:40PM +0900, Isaku Yamahata wrote:
> On Mon, Oct 18, 2010 at 07:38:53AM +0200, Michael S. Tsirkin wrote:
> > On Mon, Oct 18, 2010 at 12:17:45PM +0900, Isaku Yamahata wrote:
> > > record which is written into pci configuration space.
> > > introduce helper function to ze
Am 15.10.2010 23:11, schrieb Christoph Hellwig:
> On Fri, Oct 15, 2010 at 06:05:39PM +0200, Kevin Wolf wrote:
>> Additionally to testing the qemu-img convert -B option, also test
>> -o backing_file.
>>
>> Also, the old test acidentlly used a pattern of zeros for most of the writes,
>> so that the a
On 10/16/10 21:02, Blue Swirl wrote:
> On Sat, Oct 16, 2010 at 4:04 PM, wrote:
>> From: Jes Sorensen
>>
>> This consolidates the duplicated oom_check() functions, as well as
>> splitting them into OS dependant versions to avoid the #ifdef
>> grossness that was present in the old osdep.c version.
1 - 100 of 104 matches
Mail list logo
