On (Mon) 19 Dec 2011 [14:09:43], Zang Hongyong wrote:
> 于 2011/12/16,星期五 17:39, Amit Shah 写道:
> >On (Fri) 16 Dec 2011 [09:14:26], zanghongy...@huawei.com wrote:
> >>From: Hongyong Zang
> >>
> >>In pci_enable_msix(), the guest's virtio-serial driver tries to set msi-x
> >>with one vector per queue.
On Mon, 2011-12-19 at 17:19 +1100, y...@ozlabs.org wrote:
> From: Michael Ellerman
These are from me obviously. Thankyou POS git-send-email.
cheers
signature.asc
Description: This is a digitally signed message part
From: Michael Ellerman
The balloon option is not i386 only, so move it into the standard
options section.
Signed-off-by: Michael Ellerman
---
qemu-options.hx | 26 +-
1 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
in
From: Michael Ellerman
Only print options in the help output that are accepted by our arch.
This is less confusing for users and also for other programs that
consume the help output.
The options affected are:
-g and -prom-env only displayed on PPC or SPARC
-win2k-hack, -rtc-td-hack, -no-fd-b
From: Michael Ellerman
In vl.c and qemu-options.h we define macros and include qemu-options.def
in order to generate different content. Move the bulk of the def'ing and
undef'ing into a wrapper, this will make it cleaner when we add another
macro in the next patch.
AFAICS undefining GEN_DOCS ser
于 2011/12/16,星期五 17:39, Amit Shah 写道:
On (Fri) 16 Dec 2011 [09:14:26], zanghongy...@huawei.com wrote:
From: Hongyong Zang
In pci_enable_msix(), the guest's virtio-serial driver tries to set msi-x
with one vector per queue. But it fails and eventually all virtio-serial
ports share one MSI-X vect
On Sat, Dec 17, 2011 at 07:12, Stefan Weil wrote:
> Am 16.12.2011 04:24, schrieb TeLeMan:
>
>> On Sun, Dec 4, 2011 at 05:32, Stefan Weil wrote:
>>>
>>> Since commit 1d14ffa97eacd3cb722271eaf6f093038396eac4 (in 2005),
>>> QEMU applications on W32 don't use the default SDL compiler flags:
>>>
>>> I
On Fri, Dec 16, 2011 at 03:53:53PM +0100, Joerg Roedel wrote:
> On Thu, Dec 15, 2011 at 11:05:07AM -0700, Alex Williamson wrote:
> > Starting with it in the core and hand waving some future use that we
> > don't plan to implement right now seems like the wrong direction.
>
> I agree with Alex. Fir
On 16 December 2011 22:37, Benoît Canet wrote:
> This function is not longer in use so remove it.
>
> Signed-off-by: Benoît Canet
Nothing wrong here, but you can go further: it's now the case that
for all mmio regions s->mmio[n].memory is non-NULL, so you can remove
some if() conditionals in sys
On 16 December 2011 22:37, Benoît Canet wrote:
> Expose only one container MemoryRegion to sysbus.
> (Peter Maydell's idea)
>
> Signed-off-by: Benoît Canet
Reviewed-by: Peter Maydell
On 16 December 2011 22:37, Benoît Canet wrote:
> The isa region is not exposed as a sysbus region because the iobr
> register contains its address and use it to remap dynamically
> the region. (Peter Maydell's idea)
>
> Signed-off-by: Benoît Canet
Reviewed-by: Peter Maydell
Fix a typo that meant that ADDRESS_ERRORs setting or clearing write
protection would clear every other bit in the status register.
Signed-off-by: Peter Maydell
---
hw/sd.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/sd.c b/hw/sd.c
index e57852e..dd28061 100644
This patchset fixes a number of bugs in our SD card emulation, mostly
in the status bit handling. In particular, it fixes the issues raised
in https://bugs.launchpad.net/qemu/+bug/597641 . The others are things
I noticed while I was poking around in the code.
Patches 01-04, 07 are pretty straightf
If we fail to validate the CRC for an SD command we should be setting
COM_CRC_ERROR, not clearing it. (This bug actually has no effect currently
because sd_req_crc_validate() always returns success.)
Signed-off-by: Peter Maydell
---
hw/sd.c |2 +-
1 files changed, 1 insertions(+), 1 deletion
Add a clarifying comment about what the CARD_STATUS_[ABC]
macros are defining.
Signed-off-by: Peter Maydell
---
hw/sd.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/hw/sd.c b/hw/sd.c
index a1c98c0..245b6c3 100644
--- a/hw/sd.c
+++ b/hw/sd.c
@@ -309,6 +309,11 @@ st
Fix some bugs in our implementation of the APP_CMD status bit:
* the response to an ACMD should have APP_CMD set, not cleared
* if an illegal ACMD is sent then the next command should be
handled as a normal command
This requires that we split "card is expecting an ACMD" from
the state of the
App commands in an invalid state should set ILLEGAL_COMMAND, not
merely return a zero response.
Signed-off-by: Peter Maydell
---
hw/sd.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/sd.c b/hw/sd.c
index 9116f67..9eebfac 100644
--- a/hw/sd.c
+++ b/hw/sd.c
@@ -1262,
Add an extra sd_illegal value to the sd_rsp_type_t enum so that
sd_app_command() and sd_normal_command() can tell sd_do_command()
that the command was illegal. This is needed so we can do things
like reset certain status bits only on receipt of a valid command.
For the moment, just use it to pull o
Handle returning CRC and locked-card errors in the same code path
we use for other responses. This makes no difference in behaviour
but means that these error responses will be printed by the debug
logging code.
Signed-off-by: Peter Maydell
---
hw/sd.c |7 +--
1 files changed, 5 insertio
On Mon, 12 Dec 2011 14:45:26 +, Paul Brook wrote:
> > I can do that, but not this year (on holiday from Friday 16th, without
> > any access to Internet whatsoever :-) One think to be decided is in what
> > order the halfs should be filled? Low first, then high? High then low?
> > Does it matte
---
target-i386/kvm.c | 65 +++-
1 files changed, 63 insertions(+), 2 deletions(-)
diff --git a/target-i386/kvm.c b/target-i386/kvm.c
index 9080996..731cc8d 100644
--- a/target-i386/kvm.c
+++ b/target-i386/kvm.c
@@ -29,6 +29,7 @@
#include "hw/pc.
---
Makefile.target |2 +
target-i386/cpuid.c | 14 ++
target-i386/hyperv.c | 65 ++
target-i386/hyperv.h | 37
4 files changed, 118 insertions(+), 0 deletions(-)
create mode 100644 target-i386/hy
With the following series of patches we are starting to implement
some basic Microsoft Hyper-V Enlightenment functionality. This series
is mostly about adding support for relaxed timing, spinlock,
and virtual apic.
For more Hyper-V related information please see:
"Hypervisor Functional Specificati
Response format r6 includes a subset of the status bits;
clear the clear-on-read bits which are read by an r6 response.
Signed-off-by: Peter Maydell
---
hw/sd.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/sd.c b/hw/sd.c
index 6614cbf..2b8ebe4 100644
--- a/hw/sd.c
Fix bugs in the code determining whether to accept a card when the
SD card is locked. Most notably, we had the condition completely
reversed, so we would accept all the commands we should refuse and
refuse all the commands we should accept. Correct this by refactoring
the enormous if () clause into
Correct how we handle the type B ("cleared on valid command")
status bits. In particular, the CURRENT_STATE bits in a response
should be the state of the card when it received that command,
not the state when it received the preceding command. (This is
one of the issues noted in LP:597641.)
Signed
Thank you for subscribing. You have now unsubscribed and no more messages will
be sent.
On 12/15/2011 05:12 PM, Anthony Liguori wrote:
> On 12/09/2011 03:54 PM, Anthony PERARD wrote:
>> In Xen case, the guest RAM is not handle by QEMU, and it is saved by
>> Xen tools.
>> So, we just avoid to register the RAM save state handler.
>>
>> -register_savevm_live(NULL, "ram", 0, 4, NULL,
On 12/13/2011 01:55 PM, Stefano Stabellini wrote:
> A bit more context to my suggestion:
>
> - we open the save state file and check the magic number and the
> version number before machine->init();
>
> - we add a new set of entries to the save state file that contains
> early_savevm functions: the
On 12/12/2011 05:32 PM, Stefano Stabellini wrote:
> > Really, I think this is something inherently incompatible with the
> > current memory API. If Xen has this unfixable special "requirement"
> > (it's rather a design issue IMHO), adjust the API and adapt all devices.
> > Hot-fixing only a single
From: "Aneesh Kumar K.V"
Kernel internal values can change, add protocol values for these constant and
use them.
Signed-off-by: Aneesh Kumar K.V
---
hw/9pfs/virtio-9p.c | 47 ---
1 files changed, 24 insertions(+), 23 deletions(-)
diff --git a/hw/9
Signed-off-by: Paolo Bonzini
---
hw/qdev-properties.c | 41 ++---
hw/qdev.c|5 +
hw/qdev.h|2 ++
3 files changed, 29 insertions(+), 19 deletions(-)
diff --git a/hw/qdev-properties.c b/hw/qdev-properties.c
index f0b811c..de
Reviewed-by: Anthony Liguori
Signed-off-by: Paolo Bonzini
---
hw/qdev.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/qdev.c b/hw/qdev.c
index 83913c7..bda8d6c 100644
--- a/hw/qdev.c
+++ b/hw/qdev.c
@@ -1110,7 +1110,7 @@ void qdev_property_set(DeviceState *dev, Vis
This will be used when reject invalid values for integer fields that
are less than 64-bits wide.
Reviewed-by: Anthony Liguori
Signed-off-by: Paolo Bonzini
---
qerror.c |5 +
qerror.h |3 +++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/qerror.c b/qerror.c
index add
This patch adds a visitor interface to Property. This way, QOM will be
able to expose Properties that access a fixed field in a struct without
exposing also the everything-is-a-string "feature" of qdev properties.
Whenever the printed representation in both QOM and qdev (which is
typically the ca
Reviewed-by: Anthony Liguori
Signed-off-by: Paolo Bonzini
---
hw/qdev-properties.c | 12
hw/qdev.c|9 ++---
hw/qdev.h|1 +
3 files changed, 15 insertions(+), 7 deletions(-)
diff --git a/hw/qdev-properties.c b/hw/qdev-properties.c
index 41d2165.
Push legacy properties into a "legacy-..." namespace, and make them
available with correct types too.
For now, all properties come in both variants. This need not be the
case for string properties. We will revisit this after -device is
changed to actually use the legacy properties.
Reviewed-by:
qdev_property_get and qdev_property_set can generate permission
denied errors themselves. Do not duplicate this functionality in
qdev_get/set_legacy_property, and clean up excessive indentation.
Reviewed-by: Anthony Liguori
Signed-off-by: Paolo Bonzini
---
hw/qdev.c | 46 +++-
A NULL qobj can occur when a parameter is fetched via qdict_get, but
the parameter is not in the command. By returning NULL, the caller can
choose whether to raise a missing parameter error, an invalid parameter
type error, or use a default value. For example, qom-set could can
use this to reset
QOM right now does not have a way to communicate values for qdev
properties except as strings. This is bad.
This patch improves the Property implementation so that properties
export a visitor-based interface in addition to the string-based
interface. The new interface can then be registered as a
On 12/18/2011 05:43 PM, Peter Maydell wrote:
> On 18 December 2011 15:32, Avi Kivity wrote:
> > I missed Xen while converting stuff to the memory API, as it's not in hw/.
> >
> > Here comes the first simple patches; expect more as ram_addr_t is retired.
>
> Er, ram_addr_t is going away? Can you el
On 18 December 2011 15:32, Avi Kivity wrote:
> I missed Xen while converting stuff to the memory API, as it's not in hw/.
>
> Here comes the first simple patches; expect more as ram_addr_t is retired.
Er, ram_addr_t is going away? Can you elaborate?
-- PMM
** Changed in: qemu-kvm (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/899961
Title:
qemu/kvm locks up when run 32bit userspace with 64bit kernel
Status
Undo the private implementation of qemu_ram_alloc(); use the global one
(which calls right back into xen_ram_alloc()).
Signed-off-by: Avi Kivity
---
xen-all.c | 41 ++---
1 files changed, 22 insertions(+), 19 deletions(-)
diff --git a/xen-all.c b/xen-all.c
Currently xen_ram_alloc() relies on ram_addr, which is going away.
Give it something else to use as a cookie.
Signed-off-by: Avi Kivity
---
exec-obsolete.h |7 +--
exec.c | 10 ++
hw/xen.h|4 +++-
memory.c|6 +++---
xen-all.c |2 +-
xe
I missed Xen while converting stuff to the memory API, as it's not in hw/.
Here comes the first simple patches; expect more as ram_addr_t is retired.
Please review & test (build tested only here).
Also in
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git memory/xen
(includes a patchset not y
http://www.mail-archive.com/qemu-devel@nongnu.org/msg90256.html has some
patches from Sebastian Huber which let him run the RTEMS real time
system on the TI Stellaris LM3S6965 with a working system tick. As he
notes, some of them are hacks and not suitable for applying to qemu, but
they give a reas
On 18 December 2011 13:30, Sebastian Huber
wrote:
> I am primary a Qemu user and fixed the bugs only as far as it was necessary
> to run my test suites. I used the surrounding code as a reference. Maybe I
> find some time in the next months to clean this up.
Right. Thanks for tracking down what
On 12/18/2011 05:48 AM, Ronnie Sahlberg wrote:
This patch adds configuration variables for iSCSI to set
initiator-name to use when logging in to the target,
which type of header-digest to negotiate with the target
and username and password for CHAP authentication.
This allows specifying a initia
On 17/12/11 01:50, Peter Maydell wrote:
On 16 December 2011 18:50, Sebastian Huber
wrote:
According to "ARMv7-M Architecture Reference Manual" issue D section
"B3.2.10 System Handler Prioriy Register 1, SHPR1", "B3.2.11 System
Handler Prioriy Register 2, SHPR2", and "B3.2.12 System Handler Pri
On Tue, Dec 06, 2011 at 10:43:42AM -0600, Michael Roth wrote:
> On 12/06/2011 08:44 AM, Daniel P. Berrange wrote:
> >On Tue, Dec 06, 2011 at 08:34:06AM -0600, Michael Roth wrote:
> >>The code is still in rough shape, but while we're on the topic of guest
> >>agents
> >>I wanted to put out a workin
Am 15.12.2011 11:21, schrieb Kevin Wolf:
Am 15.12.2011 10:32, schrieb Stefan Weil:
Am 15.12.2011 06:22, schrieb Andreas Färber:
Their website has the following:
"GTK-Doc wasn't originally intended to be a general-purpose
documentation tool, so it can be a bit awkward to setup and use. For a
mo
On 18.12.2011 15:20, Stefan Weil wrote:
[]
> It looks like the autoblock was created yesterday and
> terminates automaticallytoday (see
> http://wiki.qemu.org/index.php?title=Special:BlockList&action=search&ip=%23132).
>
> That won't help much as long as the wiki thinks that everyone
> has the loc
Am 18.12.2011 11:44, schrieb Peter Maydell:
On 18 December 2011 10:38, Orit Wasserman wrote:
Hi Anthony,
I'm trying to edit a wiki page I create in qemu.org.
I get the following error:
Intended blockee: 127.0.0.1
Your current IP address is 127.0.0.1, and the block ID is #132.
This look
> > Your current IP address is 127.0.0.1, and the block ID is #132.
+1. :)
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
Homepage: http://people.cs.nctu.edu.tw/~chenwj
On 18 December 2011 10:38, Orit Wasserman wrote:
> Hi Anthony,
> I'm trying to edit a wiki page I create in qemu.org.
>
> I get the following error:
> Intended blockee: 127.0.0.1
> Your current IP address is 127.0.0.1, and the block ID is #132.
This looks very fishy ^
I get the same error,
Hi Anthony,
I'm trying to edit a wiki page I create in qemu.org.
I get the following error:
You do not have permission to edit this page, for the following reason:
Your IP address has been automatically blocked because it was used by another
user, who was blocked by Mjt.
The reason given is this
On 12/15/2011 05:30 PM, Jiri Denemark wrote:
On Thu, Dec 15, 2011 at 08:58:55 -0600, Anthony Liguori wrote:
Pass '-readconfig /etc/qemu/target-x86_64.conf' to pick up those models and if
you are absolutely insistent on not giving the user any ability to change things
on their own, cp the file fr
On 12/15/2011 11:02 PM, Jordan Justen wrote:
> I verified that 'info mtree' and 'info qdev' are equivalent for pc-1.0
> when using master and with my patches.
>
> However, I did discover that v1.0 seems to differ from master for this
> same test.
>
That's are fine; pre-memory-API devices don't sho
On Thu, Dec 15, 2011 at 03:42:44PM +, Daniel P. Berrange wrote:
> On Thu, Dec 15, 2011 at 03:54:15PM +0100, Jiri Denemark wrote:
> > Hi,
> >
> > Recently I realized that all modern CPU models defined in
> > /etc/qemu/target-x86_64.conf are useless when qemu is used through libvirt.
> > That's
Thank you for subscribing. You have now unsubscribed and no more messages will
be sent.
61 matches
Mail list logo
