On 18.03.2011, at 05:03, David Gibson wrote:
> On Thu, Mar 17, 2011 at 08:20:52AM -0500, Anthony Liguori wrote:
>> On 03/16/2011 11:55 PM, David Gibson wrote:
>>> On Wed, Mar 16, 2011 at 03:44:49PM -0500, Anthony Liguori wrote:
On 03/15/2011 11:56 PM, David Gibson wrote:
> [snip]
Is th
** Changed in: qemu
Status: New => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/712337
Title:
connecthon basic test5 failed with qemu 0.14 on Virtfs path in guest
Status in QEM
This defect is not seen with latest qemu.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/712337
Title:
connecthon basic test5 failed with qemu 0.14 on Virtfs path in guest
Status in QEMU:
In Prog
On 03/11/2011 08:35 AM, Benjamin Poirier wrote:
Here is version 6 of my patchset to add vlan support to the emulated rtl8139
nic.
Changes since v5:
* moved all receive changes to "add vlan tag extraction"
* fixed checkpatch.pl style issues
* fixed bugs in receive case rel
On Thu, Mar 17, 2011 at 08:20:52AM -0500, Anthony Liguori wrote:
> On 03/16/2011 11:55 PM, David Gibson wrote:
> >On Wed, Mar 16, 2011 at 03:44:49PM -0500, Anthony Liguori wrote:
> >>On 03/15/2011 11:56 PM, David Gibson wrote:
[snip]
> >>Is the hypercall handler ever specific to a CPU?
> >If you me
On 03/17/2011 10:26 AM, Markus Armbruster wrote:
Kevin Wolf writes:
Am 15.03.2011 14:37, schrieb Anthony Liguori:
On 03/15/2011 06:21 AM, Kevin Wolf wrote:
Am 14.03.2011 18:48, schrieb Anthony Liguori:
I've got a spec written up at http://wiki.qemu.org/Features/QCFG.
Initial code is in my Q
On 03/17/2011 11:10 AM, Антон Кочков wrote:
Looks like.
From Russia also
We're back online. The VM didn't reboot properly because of a
management tool issue. Sorry for the inconvenience.
Regards,
Anthony Liguori
Best regards,
Anton Kochkov.
On Thu, Mar 17, 2011 at 18:19, François R
Add both chroot worker and qemu side interfaces to create special files
(directory, device nodes, links and symbolic links)
Signed-off-by: M. Mohan Kumar
---
hw/9pfs/virtio-9p-chroot-worker.c | 52
hw/9pfs/virtio-9p-chroot.h|5 +++
hw/9pfs/virtio-9p-loc
9p Chroot environment needs APIs defined in qemu-thread.c, so enable
CONFIG_THREAD if virtfs is enabled
Signed-off-by: M. Mohan Kumar
---
configure |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/configure b/configure
index 2560357..9eddd38 100755
--- a/configure
+++ b/c
Support renaming a file or directory in chroot envirnoment. Add
interfaces for renaming in chroot worker and qemu side.
Signed-off-by: M. Mohan Kumar
---
hw/9pfs/virtio-9p-chroot-worker.c | 17 +
hw/9pfs/virtio-9p-chroot.h|1 +
hw/9pfs/virtio-9p-local.c |
Add both chroot worker & qemu side interfaces to create regular files in
chroot environment
Signed-off-by: M. Mohan Kumar
---
hw/9pfs/virtio-9p-chroot-worker.c | 36
hw/9pfs/virtio-9p-chroot.h|1 +
hw/9pfs/virtio-9p-local.c |5 +++--
This patch adds both chroot worker and qemu side support to open a file/
directory in the chroot environment
Signed-off-by: M. Mohan Kumar
---
hw/9pfs/virtio-9p-chroot.c | 29 +++
hw/9pfs/virtio-9p-chroot.h |2 +-
hw/9pfs/virtio-9p-local.c | 80 ++
QEMU side interfaces to communicate with chroot worker process.
Signed-off-by: M. Mohan Kumar
---
Makefile.objs |2 +-
hw/9pfs/virtio-9p-chroot.c | 92
hw/9pfs/virtio-9p-chroot.h |1 +
3 files changed, 94 insertions(+), 1 deleti
Add qemu_read_full function
Signed-off-by: M. Mohan Kumar
---
osdep.c | 32
qemu-common.h |2 ++
2 files changed, 34 insertions(+), 0 deletions(-)
diff --git a/osdep.c b/osdep.c
index 327583b..8d84a88 100644
--- a/osdep.c
+++ b/osdep.c
@@ -127,6 +127
Add support to do chown in chroot process
Signed-off-by: M. Mohan Kumar
---
hw/9pfs/virtio-9p-chroot-worker.c | 18 ++
hw/9pfs/virtio-9p-chroot.h|1 +
hw/9pfs/virtio-9p-local.c |9 +
3 files changed, 24 insertions(+), 4 deletions(-)
diff --git a
Implement chroot worker side interfaces like sending the file
descriptor to qemu process, reading the object request from socket etc.
Also add chroot main function and other helper routines.
Signed-off-by: M. Mohan Kumar
---
Makefile.objs |1 +
hw/9pfs/virtio-9p-chroot-wo
Add support to do chmod operation in chroot process.
Signed-off-by: M. Mohan Kumar
---
hw/9pfs/virtio-9p-chroot-worker.c | 18 ++
hw/9pfs/virtio-9p-chroot.h|1 +
hw/9pfs/virtio-9p-local.c |5 +++--
3 files changed, 22 insertions(+), 2 deletions(-)
diff
Support for removing file or directory in chroot environment. Add
interfaces to remove file/directory in chroot worker and qemu side.
Signed-off-by: M. Mohan Kumar
---
hw/9pfs/virtio-9p-chroot-worker.c | 34 ++
hw/9pfs/virtio-9p-chroot.h|1 +
hw/9pfs
Add chroot functionality for systemcalls that can operate on a file
using relative directory file descriptor.
Signed-off-by: M. Mohan Kumar
---
hw/9pfs/virtio-9p-local.c | 114 +
1 files changed, 104 insertions(+), 10 deletions(-)
diff --git a/hw/9pf
After creating a file object, its permission and ownership details are updated
as per 9p client's request for both passthrough and none security model.
But with chrooted environment its not required for passthrough security model.
Move all post file creation changes to none security model.
Signed-
In passthrough security model, following symbolic links in the server
side could result in TOCTTOU vulnerabilities.
This patchset resolves this issue by creating a dedicated process which
chroots into the share path and all file object access is done in the
chroot environment.
This patchset imple
On Wed, Mar 16, 2011 at 05:20:53PM -0500, Anthony Liguori wrote:
> On 03/15/2011 11:56 PM, David Gibson wrote:
> >From: Ben Herrenschmidt
[snip]
> >+static target_ulong h_put_tce(CPUState *env, sPAPREnvironment *spapr,
> >+ target_ulong opcode, target_ulong *args)
> >+{
It looks good, except the unnecessary black line after return 0;
Reviewed-by: Isaku Yamahata
On Thu, Mar 17, 2011 at 01:00:54PM +0300, Michael Tokarev wrote:
> This patch almost rewrites acpi_table_add() function
> (but still leaves it using old get_param_value() interface).
> The result is that
Introduce accessor function to know INTx levels.
It will be used later by q35.
Although piix_pci tracks the intx line levels, it can be eliminated
by this helper function.
Cc: Michael S. Tsirkin
Signed-off-by: Isaku Yamahata
---
hw/pci.c |7 +++
hw/pci.h |1 +
2 files changed, 8 ins
On Thu, Mar 17, 2011 at 04:41:08PM +0200, Michael S. Tsirkin wrote:
> > +static int piix3_post_load(void *opaque, int version_id)
> > +{
> > +PIIX3State *piix3 = opaque;
> > +piix3_rebuild_irq_levels(piix3);
>
> Don't we need to set_irq_pic here as well?
> And in that case, just make the
PIIX3State::pci_irq_levels are redundant which is already tracked by
PCIBus layer. So eliminate them.
Cc: Michael S. Tsirkin
Signed-off-by: Isaku Yamahata
---
hw/piix_pci.c | 31 +--
1 files changed, 21 insertions(+), 10 deletions(-)
diff --git a/hw/piix_pci.c b/h
optimize irq routing in piix_pic.c which has been a TODO.
So far piix3 tracks each pirq level and checks whether a given pic pins is
asserted by seeing if each pirq is mapped into the pic pin.
This is independent on irq routing, but data path is on slow path.
Given that irq routing is rarely chang
This patch series optimizes irq data path of piix_pci.
So far piix3 tracks each pirq level and checks whether a given pic pins is
asserted by seeing if each pirq is mapped into the pic pin.
This is independent on irq routing, but data path is on slow path.
Given that irq routing is rarely changed
We have two bits that can represent kvmclock in cpuid.
They signal the guest which msr set to use. When we tweak flags
involving this value - specially when we use "-", we have to act on both.
Besides adding it to the kvm features list, we also have to "break" the
assumption represented by the bre
kvmclock presence can be signalled by two different flags. So for
device creation, we have to test for both.
Signed-off-by: Glauber Costa
---
hw/kvmclock.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/hw/kvmclock.c b/hw/kvmclock.c
index b6ceddf..004c4ad 100644
--
According to Avi's comments over my last submission, I decided to take a
different, and more correct direction - we hope.
This patch is now using the features provided by KVM_GET_SUPPORTED_CPUID
directly to
mask out features from guest-visible cpuid.
The old get_para_features() mechanism is kept
This patch is a follow up to an earlier one that aims to enable
kvmclock newer msr set. This time I'm doing it through a more sane
mechanism of consulting the kernel about the supported msr set.
Glauber Costa (3):
use kernel-provided para_features instead of statically coming up
with new cap
Hi, I have experienced the loopback mode failed on the interfaces. Just
wondering is loopback mode is supported on the QEMU e1000 driver?
Thanks,
Amy
On 03/17/2011 10:22 AM, Markus Armbruster wrote:
void qcfg_handle_vnc(VncConfig *option, Error **errp)
{
}
And that's it. You can squirrel away the option such that they all
can be processed later, you can perform additional validation and
return an error, or you can implement the appropriate
On Thu, Mar 17, 2011 at 3:11 PM, Kevin Wolf wrote:
> Am 17.03.2011 15:44, schrieb Daniel P. Berrange:
>> On Tue, Mar 15, 2011 at 03:11:32PM +0100, Christoph Hellwig wrote:
>>> Add a new bdrv_change_cache that can set/clear the writeback flag
>>> at runtime by stopping all I/O and closing/reopening
On 03/17/2011 09:04 AM, Kevin Wolf wrote:
No, the problem with the old events is that they aren't
registered/maskable. So even if you don't care about BLOCK_IO_ERROR,
you're getting the notification. Plus, we'd like to add the ability to
add a tag to events when we register them.
What's the
Michael Tokarev writes:
> 17.03.2011 16:51, Markus Armbruster wrote:
>> Michael Tokarev writes:
>>
>>> Trivial patch. I've sent it yesterday but somehow it didn't
>>> reach the list.
>>>
>>> This fixes the problem when qemu continues even if -drive specification
>>> is somehow invalid, resulti
On Thu, Mar 17, 2011 at 03:19:28PM +0100, Jes Sorensen wrote:
> On 03/17/11 11:45, Alon Levy wrote:
> > On Thu, Mar 17, 2011 at 11:29:03AM +0100, Jes Sorensen wrote:
> >> On 03/17/11 11:27, Alon Levy wrote:
> >>> On Thu, Mar 17, 2011 at 10:48:43AM +0100, Jes Sorensen wrote:
> > Same for the ass
On Thu, Mar 17, 2011 at 04:45:15PM +, Stefan Hajnoczi wrote:
> On Thu, Mar 17, 2011 at 3:00 PM, Alon Levy wrote:
> > On Thu, Mar 17, 2011 at 04:49:26PM +0200, Alon Levy wrote:
> >> ---
> >> Makefile | 32
> >> Makefile.objs | 32 ++
Am 17.03.2011 16:33, schrieb Markus Armbruster:
> Kevin Wolf writes:
>
>> Am 17.03.2011 08:58, schrieb Michael Tokarev:
>>> Trivial patch. I've sent it yesterday but somehow it didn't
>>> reach the list.
>>>
>>> This fixes the problem when qemu continues even if -drive specification
>>> is someh
On Thu, Mar 17, 2011 at 3:00 PM, Alon Levy wrote:
> On Thu, Mar 17, 2011 at 04:49:26PM +0200, Alon Levy wrote:
>> ---
>> Makefile | 32
>> Makefile.objs | 32
>> 2 files changed, 32 insertions(+), 32 deletions(-)
>
> The c
I am pleased to report that a short of version of the FVD-cow paper I
previously posted here was just accepted to USENIX Annual Technical
Conference (USENIX ATC'11), which is a prestigious and highly competitive
research conference in the systems field. This shows from another angle
(in additio
On 03/17/2011 11:10 AM, Антон Кочков wrote:
Looks like.
From Russia also
The server is down. The VM was having what appeared to be memory issues
(random processes SEGV'ing) over the past week. I can't say for sure
whether it's an issue with the guest or whether it's an issue with the
phys
Am 17.03.2011 16:49, schrieb Michael Tokarev:
> 17.03.2011 18:04, Kevin Wolf wrote:
>> Am 17.03.2011 08:58, schrieb Michael Tokarev:
> []
>>> --- a/vl.c
>>> +++ b/vl.c
>>> @@ -2098,7 +2098,8 @@ int main(int argc, char **argv, char **envp)
>>>HD_OPTS);
>>>
At least from france, confirmed by several people.
François.
traceroute to qemu.org (64.62.173.86), 64 hops max, 52 byte packets
1 172.28.0.1 (172.28.0.1) 1.145 ms 0.960 ms 0.859 ms
2 172.30.1.1 (172.30.1.1) 0.702 ms 0.786 ms 0.631 ms
3 routeur-iut.iut-valence.fr (193.51.172.1) 1.207
17.03.2011 18:04, Kevin Wolf wrote:
> Am 17.03.2011 08:58, schrieb Michael Tokarev:
[]
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -2098,7 +2098,8 @@ int main(int argc, char **argv, char **envp)
>>HD_OPTS);
>> break;
>> case QEMU_OPTION_drive:
>> -
Kevin Wolf writes:
> Am 17.03.2011 08:58, schrieb Michael Tokarev:
>> Trivial patch. I've sent it yesterday but somehow it didn't
>> reach the list.
>>
>> This fixes the problem when qemu continues even if -drive specification
>> is somehow invalid, resulting in a mess. Applicable for both cur
Looks like.
>From Russia also
Best regards,
Anton Kochkov.
On Thu, Mar 17, 2011 at 18:19, François Revol wrote:
> At least from france, confirmed by several people.
>
> François.
>
> traceroute to qemu.org (64.62.173.86), 64 hops max, 52 byte packets
> 1 172.28.0.1 (172.28.0.1) 1.145 ms 0
On Thu, Mar 17, 2011 at 04:49:26PM +0200, Alon Levy wrote:
> ---
> Makefile | 32
> Makefile.objs | 32
> 2 files changed, 32 insertions(+), 32 deletions(-)
The commit message can be a little more verbose :(
It will be:
On 03/17/2011 10:19 AM, François Revol wrote:
At least from france, confirmed by several people.
François.
traceroute to qemu.org (64.62.173.86), 64 hops max, 52 byte packets
1 172.28.0.1 (172.28.0.1) 1.145 ms 0.960 ms 0.859 ms
2 172.30.1.1 (172.30.1.1) 0.702 ms 0.786 ms 0.631 ms
Am 17.03.2011 15:44, schrieb Daniel P. Berrange:
> On Tue, Mar 15, 2011 at 03:11:32PM +0100, Christoph Hellwig wrote:
>> Add a new bdrv_change_cache that can set/clear the writeback flag
>> at runtime by stopping all I/O and closing/reopening the image file.
>>
>> All code is based on a patch from
Alex, Michael,
Thank you for the clarification.
On Tue, Mar 15, 2011 at 1:01 AM, Alex Williamson wrote:
> On Mon, 2011-03-14 at 21:00 +0200, Michael S. Tsirkin wrote:
> > On Mon, Mar 14, 2011 at 10:35:08PM +0530, rukhsana ansari wrote:
> > > Seeking clarification to the original question I post
Kevin Wolf writes:
> Am 15.03.2011 14:37, schrieb Anthony Liguori:
>> On 03/15/2011 06:21 AM, Kevin Wolf wrote:
>>> Am 14.03.2011 18:48, schrieb Anthony Liguori:
I've got a spec written up at http://wiki.qemu.org/Features/QCFG.
Initial code is in my QAPI tree.
>>> One question about a s
On Thu, Mar 17, 2011 at 04:43:36PM +0200, Michael S. Tsirkin wrote:
> On Wed, Mar 16, 2011 at 06:29:14PM +0900, Isaku Yamahata wrote:
> > introduce pci_swizzle_map_irq_fn() for interrupt pin swizzle which is
> > standardized. PCI bridge swizzle is common logic, by introducing
> > this function dupl
Anthony Liguori writes:
> As I've been waiting for QAPI review, I've been working on the design
> of a new mechanism to replace our current command line option handling
> (QemuOpts) with something that reuses the QAPI infrastructure.
I'm ignoring the connection to QAPI, because I'm still ignoran
From: Robert Relyea
In this mode libcacard doesn't emulate a card, but just passes apdu's
straight to the underlying card.
Not to be confused with ccid-card-passthru, which doesn't use libcacard
at all. So with this functionality in libcacard you can talk directly
to the host accessible card, fo
Am 17.03.2011 08:58, schrieb Michael Tokarev:
> Trivial patch. I've sent it yesterday but somehow it didn't
> reach the list.
>
> This fixes the problem when qemu continues even if -drive specification
> is somehow invalid, resulting in a mess. Applicable for both current
> master and for stable
This devices uses libcacard (internal) to emulate a smartcard conforming
to the CAC standard. It attaches to the usb-ccid bus. Usage instructions
(example command lines) are in the following patch in docs/ccid.txt. It
uses libcacard which uses nss, so it can work with both hw cards and
certificates
This patchset adds three new devices, usb-ccid, ccid-card-passthru and
ccid-card-emulated, providing a CCID bus, a simple passthru protocol
implementing card requiring a client, and a standalone emulated card.
It also introduces a new directory libcaccard with CAC card emulation,
CAC is a type of
Add documentation for the usb-ccid device and accompanying two card
devices, ccid-card-emulated and ccid-card-passthru.
Signed-off-by: Alon Levy
---
docs/ccid.txt | 135 +
1 files changed, 135 insertions(+), 0 deletions(-)
create mode 100
qemu-thread.h relies on uint64_t being defined, but doesn't include
inttypes.h explicitly. This makes it easier to use it from vscclient (part
of libcacard).
---
qemu-thread.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/qemu-thread.h b/qemu-thread.h
index acdb6b2..b14
A CCID device is a smart card reader. It is a USB device, defined at [1].
This patch introduces the usb-ccid device that is a ccid bus. Next patches will
introduce two card types to use it, a passthru card and an emulated card.
[1] http://www.usb.org/developers/devclass_docs/DWG_Smart-Card_CCID_R
From: Robert Relyea
client to talk to ccid-card-passthru and use smartcard on client to
perform actual operations.
---
libcacard/Makefile|7 +-
libcacard/vscclient.c | 730 +
2 files changed, 736 insertions(+), 1 deletions(-)
create mode
---
Signed-off-by: Alon Levy
v20->v21 changes: (Jes Sorenson review)
* license set to 2+
* long comment fixes, remove empty line at eof.
* add reference to COPYING
v19->v20 changes:
* checkpatch.pl
v15->v16 changes:
Protocol change:
* VSCMsgInit capabilities and magic
* removed ReaderRe
---
Makefile | 32
Makefile.objs | 32
2 files changed, 32 insertions(+), 32 deletions(-)
diff --git a/Makefile b/Makefile
index eca4c76..5b35b9f 100644
--- a/Makefile
+++ b/Makefile
@@ -112,38 +112,6 @@ ui/vnc.o: QEMU_CFL
The passthru ccid card is a device sitting on the usb-ccid bus and
using a chardevice to communicate with a remote device using the
VSCard protocol defined in libcacard/vscard_common.h
Usage docs available in following patch in docs/ccid.txt
Signed-off-by: Alon Levy
---
Changes from v20->v21:
From: Robert Relyea
---
docs/libcacard.txt | 483
1 files changed, 483 insertions(+), 0 deletions(-)
create mode 100644 docs/libcacard.txt
diff --git a/docs/libcacard.txt b/docs/libcacard.txt
new file mode 100644
index 000..5dee6fa
---
On Tue, Mar 15, 2011 at 03:11:32PM +0100, Christoph Hellwig wrote:
> Add a new bdrv_change_cache that can set/clear the writeback flag
> at runtime by stopping all I/O and closing/reopening the image file.
>
> All code is based on a patch from Prerna Saxena
> with minimal refactoring.
>
> Signed
On Wed, Mar 16, 2011 at 06:29:14PM +0900, Isaku Yamahata wrote:
> introduce pci_swizzle_map_irq_fn() for interrupt pin swizzle which is
> standardized. PCI bridge swizzle is common logic, by introducing
> this function duplicated swizzle logic will be avoided later.
>
> Cc: Michael S. Tsirkin
> S
On Thu, Mar 17, 2011 at 10:49:50PM +0900, Isaku Yamahata wrote:
> This patch series optimizes irq data path of piix_pci.
> So far piix3 tracks each pirq level and checks whether a given pic pins is
> asserted by seeing if each pirq is mapped into the pic pin.
> This is independent on irq routing, b
On Thu, Mar 17, 2011 at 10:49:53PM +0900, Isaku Yamahata wrote:
> optimize irq routing in piix_pic.c which has been a TODO.
>
> Cc: Michael S. Tsirkin
> Signed-off-by: Isaku Yamahata
Some minor comments, and looks like load has a minor bug -
probably an old one as we didn't use to have a post l
On 03/17/11 11:45, Alon Levy wrote:
> On Thu, Mar 17, 2011 at 11:29:03AM +0100, Jes Sorensen wrote:
>> On 03/17/11 11:27, Alon Levy wrote:
>>> On Thu, Mar 17, 2011 at 10:48:43AM +0100, Jes Sorensen wrote:
> Same for the asserts below, writes are from spice server thread, reads
> are in ioth
On 03/17/11 11:54, Alon Levy wrote:
> On Mon, Mar 14, 2011 at 04:41:02PM +0100, Jes Sorensen wrote:
>>> +static const char *emul_event_to_string(uint32_t emul_event)
>>> +{
>>> +switch (emul_event) {
>>> +case EMUL_READER_INSERT: return "EMUL_READER_INSERT";
>>> +case EMUL_READER_REMOVE
Hello all
I am seeing, perhaps unsurprisingly, a skewed system clock after pausing
and then resuming a qemu-kvm guest. The guest continues with its earlier
time.
Since I'd like to use the pause technique for backups, which can take 1
hour, this is significant.
This is with windows guests, and it d
Have you checked with Windows Time service enabled in the guest?
net start w32time
Best Regards,
Timur
2011/3/17 Virtbie :
> Hello all
> I am seeing, perhaps unsurprisingly, a skewed system clock after pausing
> and then resuming a qemu-kvm guest. The guest continues with its earlier
> time.
>
17.03.2011 16:51, Markus Armbruster wrote:
> Michael Tokarev writes:
>
>> Trivial patch. I've sent it yesterday but somehow it didn't
>> reach the list.
>>
>> This fixes the problem when qemu continues even if -drive specification
>> is somehow invalid, resulting in a mess. Applicable for both
On Thu, Mar 17, 2011 at 03:36:08PM +1030, Rusty Russell wrote:
> > I'm happ to switch strcmp.
>
> Of course, that's assuming buf is nul terminated.
It's the string the user writes into it, which normally should be
nul-terminated.
> > No, it's intentional. config space writes can't return errors
Am 17.03.2011 14:28, schrieb Anthony Liguori:
> On 03/17/2011 08:15 AM, Kevin Wolf wrote:
>> Am 17.03.2011 13:46, schrieb Anthony Liguori:
>>> On 03/17/2011 07:21 AM, Kevin Wolf wrote:
>> Another detail is that, event extension is more important than command
>> extension, because it's proba
Michael Tokarev writes:
> Trivial patch. I've sent it yesterday but somehow it didn't
> reach the list.
>
> This fixes the problem when qemu continues even if -drive specification
> is somehow invalid, resulting in a mess. Applicable for both current
> master and for stable-0.14 (and 0.13 and 0
optimize irq routing in piix_pic.c which has been a TODO.
Cc: Michael S. Tsirkin
Signed-off-by: Isaku Yamahata
---
hw/piix_pci.c | 103 +---
1 files changed, 90 insertions(+), 13 deletions(-)
diff --git a/hw/piix_pci.c b/hw/piix_pci.c
index
PIIX3State::pci_irq_levels are redundant which is already tracked by
PCIBus layer. So eliminate them.
Cc: Michael S. Tsirkin
Signed-off-by: Isaku Yamahata
---
hw/piix_pci.c | 31 +--
1 files changed, 21 insertions(+), 10 deletions(-)
diff --git a/hw/piix_pci.c b/h
This patch series optimizes irq data path of piix_pci.
So far piix3 tracks each pirq level and checks whether a given pic pins is
asserted by seeing if each pirq is mapped into the pic pin.
This is independent on irq routing, but data path is on slow path.
Given that irq routing is rarely changed
Introduce accessor function to know INTx levels.
It will be used later by q35.
Although piix_pci tracks the intx line levels, it can be eliminated
by this helper function.
Cc: Michael S. Tsirkin
Signed-off-by: Isaku Yamahata
---
hw/pci.c |7 +++
hw/pci.h |1 +
2 files changed, 8 ins
On Mon, Mar 14, 2011 at 04:20:22PM +0100, Jes Sorensen wrote:
> On 02/23/11 12:20, Alon Levy wrote:
> > +/* private data for PKI applets */
> > +typedef struct CACPKIAppletDataStruct {
> > +unsigned char *cert;
> > +int cert_len;
> > +unsigned char *cert_buffer;
> > +int cert_buffer
On 03/17/2011 08:15 AM, Kevin Wolf wrote:
Am 17.03.2011 13:46, schrieb Anthony Liguori:
On 03/17/2011 07:21 AM, Kevin Wolf wrote:
Another detail is that, event extension is more important than command
extension, because it's probably going to happen. I think it would be very
bad to add new even
On 03/16/2011 11:55 PM, David Gibson wrote:
On Wed, Mar 16, 2011 at 03:44:49PM -0500, Anthony Liguori wrote:
On 03/15/2011 11:56 PM, David Gibson wrote:
From: David Gibson
PowerPC and POWER chips since the POWER4 and 970 have a special
hypervisor mode, and a corresponding form of the system ca
On 03/16/2011 08:34 PM, David Gibson wrote:
+/*
+ * ICP: Presentation layer
+ */
+
+struct icp_server_state {
+uint32_t cppr :8;
+uint32_t xisr :24;
No real reason to use bitfields here.
Well.. in the hardware xics implementation, CPPR and XISR are
considered fields of the one 32-bit
Am 17.03.2011 13:46, schrieb Anthony Liguori:
> On 03/17/2011 07:21 AM, Kevin Wolf wrote:
>>>
Another detail is that, event extension is more important than command
extension, because it's probably going to happen. I think it would be very
bad to add new events just because we wanted
On 03/17/2011 07:21 AM, Kevin Wolf wrote:
Another detail is that, event extension is more important than command
extension, because it's probably going to happen. I think it would be very
bad to add new events just because we wanted to add a new field.
The way this is typically handled is that
Am 16.03.2011 16:59, schrieb Anthony Liguori:
> On 03/16/2011 09:34 AM, Luiz Capitulino wrote:
>> On Fri, 11 Mar 2011 17:05:30 -0600
>> Anthony Liguori wrote:
>>
>>> For more information about the background of QAPI, see
>>> http://wiki.qemu.org/Features/QAPI
>>>
>>> This series depends on 'QAPI R
On Wed, 16 Mar 2011 15:09:58 +0100, Christoph Hellwig wrote:
> On Wed, Mar 16, 2011 at 02:39:39PM +1030, Rusty Russell wrote:
> > > + if (strncmp(buf, "write through", sizeof("write through") - 1) == 0) {
> > > + ;
> > > + } else if (strncmp(buf, "write back", sizeof("write back") - 1) ==
On 17.03.11 13:09 , "ext Tristan Gingold" wrote:
>On Mar 17, 2011, at 11:28 AM, François Revol wrote:
>
>>From the content of the functions called it's either one of the added
>>fds which cause problem on select() (but why ?), or likely some signal
>>masks which interfere with some internal thre
On Mar 17, 2011, at 11:28 AM, François Revol wrote:
> Hi,
>
> Le 16 mars 2011 à 08:57, Tristan Gingold a écrit :
>
>>> It should fix the build issue.
>>> But QEMU is unreliable on OSX even when it gets built.
>>> I tried to bisect but lost some time trying to find a revision that
>>> actually
On Thu, Mar 17, 2011 at 12:54:16PM +0200, Alon Levy wrote:
sorry for the double review of the review, nothing new here.
> On Mon, Mar 14, 2011 at 04:41:02PM +0100, Jes Sorensen wrote:
> > On 02/23/11 12:20, Alon Levy wrote:
> > > diff --git a/hw/ccid-card-emulated.c b/hw/ccid-card-emulated.c
> >
On Mon, Mar 14, 2011 at 04:41:02PM +0100, Jes Sorensen wrote:
> On 02/23/11 12:20, Alon Levy wrote:
> > diff --git a/hw/ccid-card-emulated.c b/hw/ccid-card-emulated.c
> > new file mode 100644
> > index 000..bd84d45
> > --- /dev/null
> > +++ b/hw/ccid-card-emulated.c
> > @@ -0,0 +1,599 @@
> > +/
On Thu, Mar 17, 2011 at 11:29:03AM +0100, Jes Sorensen wrote:
> On 03/17/11 11:27, Alon Levy wrote:
> > On Thu, Mar 17, 2011 at 10:48:43AM +0100, Jes Sorensen wrote:
> >>> Same for the asserts below, writes are from spice server thread, reads
> >>> are in iothread.
> >>
> >> But shouldn't this make
Hello.
What's the possible way(s) to set OEM identification
string in BIOS too, so that it provides ACPI tables
with the given identification?
It is needed to support running OEM version of windows
vista and windows 7 (for example) from /dev/sda without
voiding its activation - this needs a real
On Tue, Mar 15, 2011 at 12:06:06PM -0700, Chris Wright wrote:
> * Anthony Liguori (anth...@codemonkey.ws) wrote:
> > On 03/15/2011 09:53 AM, Chris Wright wrote:
> > > QAPI
>
> > >- c library implementation is critical to have unit tests and test
> > > driven development
> > > - thread safe?
>
On 03/17/11 11:27, Alon Levy wrote:
> On Thu, Mar 17, 2011 at 10:48:43AM +0100, Jes Sorensen wrote:
>>> Same for the asserts below, writes are from spice server thread, reads
>>> are in iothread.
>>
>> But shouldn't this make it try to reconnect? Even if the reconnect
>> fails, it shouldn't kill th
On Thu, Mar 17, 2011 at 10:48:43AM +0100, Jes Sorensen wrote:
> On 03/17/11 10:32, Alon Levy wrote:
> > On Wed, Mar 16, 2011 at 05:48:41PM +0100, Jes Sorensen wrote:
> >> > On 03/16/11 16:52, Alon Levy wrote:
> >>> > > +void qxl_server_request_cursor_set(PCIQXLDevice *qxl, QEMUCursor *c,
> >>> > >
1 - 100 of 119 matches
Mail list logo
