Dear Sir or Madam,
We, Great Marking (HK) Industry Co., Limited (i.e. GMK), supply quartz
crystals, oscillators, ceramic resonators and filters with good quality and
very competitive price. Hope to be a partner of your company!
E-catalog will be provided if needed. FREE SAMPLES can be sen
Hi Peter,
> > 1. cpu_unlink_tb (exec.c)
>
> This function is broken even for pure TCG -- we know it has a race condition.
> As I said on IRC, I think that the right thing to do is to start
> by overhauling the current TCG code so that it is:
> (a) properly multithreaded (b) race condition free
On 11/30/2011 10:27 PM, Erik Rull wrote:
Erik, if you can test on your Debian 4.0 installation, that would be
nice. Thanks!
I will do so. Can you provide me a snapshot (.tgz) of the git? I have
heard that there are possibilities to create the tgz over some web
interfaces of git, but I didn't fi
On Wed, Nov 30, 2011 at 09:35:36PM +0100, Hervé Poussineau wrote:
> This small patchset fixes some problems I've found while using
> the dump backend.
> At least first patch may be considered for 1.0.
>
> Changes v1->v2:
> - Update patches descriptions
Reviewed-by: Stefan Hajnoczi
On Thu, Dec 01, 2011 at 11:50:24AM +0800, 陳韋任 wrote:
> > I don't see any better approach to debugging this than the one you're
> > already taking. Try to run as many workloads as you can and see if they
> > break :). Oh and always make the optimization optional, so that you can
> > narrow it dow
On Wed, Nov 30, 2011 at 03:03:31PM -0600, Anthony Liguori wrote:
> +/**
> + * @DevicePropertyEtter - called when trying to get/set a property
An established term for this is an "accessor". I've never heard "etter"
before and it looks like a typo on first sight ;).
> +/**
> + * @qdev_property_set
On Wed, Nov 30, 2011 at 03:03:32PM -0600, Anthony Liguori wrote:
> +static void qdev_set_legacy_property(DeviceState *dev, Visitor *v, void
> *opaque,
> + const char *name, Error **errp)
> +{
> +Property *prop = opaque;
> +
> +if (dev->state != DEV_STATE
> Misgenerated code might not be an issue now since we have tested our
> framework
> in LLVM-only mode. I think the problem still is about the link/unlink stuff.
> The first problem I have while lowering the threshold is the broken one
> generate
> a few traces (2, actually) that a work one does
On 1 December 2011 07:46, Stefan Hajnoczi wrote:
> It would be interesting to use an optimized interpreter instead of TCG,
> then go to LLVM for hot traces. This is more HotSpot-like with the idea
> being that the interpreter runs through initialization and rarely
> executed code without a transl
On 11/30/2011 06:22 PM, Andreas Färber wrote:
> The problem is not with the 0xfff00 region, that one works fine with 12
> and 16 bit pages so far.
>
> What I'm seeing is a crash of the very first TB at PC 0x02010, which is
> in a 4K RAM region from 0x0 on, with 16 bit pages. Also happens with v2.
On 11/30/2011 05:26 PM, Andreas Färber wrote:
> Commit 95c318f5e1f88d7e5bcc6deac17330fd4806a2d3 (Fix segfault in mmio
> subpage handling code.) prevented a segfault by making all subpage
> registrations over an existing memory page perform an unassigned access.
> Symptoms were writes not taking eff
Hi, Stefan
> It would be interesting to use an optimized interpreter instead of TCG,
> then go to LLVM for hot traces. This is more HotSpot-like with the idea
> being that the interpreter runs through initialization and rarely
> executed code without a translation overhead. For the hot paths LLV
On 11/29/2011 09:10 PM, Markus Armbruster wrote:
> Avi Kivity writes:
>
> > On 11/29/2011 05:51 PM, Juan Quintela wrote:
> >> How to do high level stuff?
> >> - python?
> >>
> >
> > One of the disadvantages of the various scripting languages is the lack
> > of static type checking, which makes it
On Thu, Dec 01, 2011 at 11:29:48AM +0200, Avi Kivity wrote:
> On 11/30/2011 05:26 PM, Andreas Färber wrote:
> > Commit 95c318f5e1f88d7e5bcc6deac17330fd4806a2d3 (Fix segfault in mmio
> > subpage handling code.) prevented a segfault by making all subpage
> > registrations over an existing memory page
>> There's no attachment in this mail. I can try to help you resolving it
>> if you provide more information.
>
> Sorry about that, see the attachment please. What kind of information you
> want
> to know?
If your code is available online I can try it myself, the question is
where is it hosted t
On 12/01/2011 11:37 AM, Gleb Natapov wrote:
> >
> > Looks reasonable. Should go into 1.1. Should we backport it to
> > 1.0.blah? From 95c318f's description, it doesn't happen in normal
> > circumstances.
> >
> To reproduce that I mappped subpage PCI bar over RAM IIRC.
In qemu 1.0, you can no
On Fri, Nov 25, 2011 at 5:01 PM, Andreas Färber wrote:
> Hi,
>
> Am 25.11.2011 16:23, schrieb Ignacio Geli:
>> Im trying to run a solaris 2.5.1 vm acording the instructions of i found
>> in this blog:
>> http://tyom.blogspot.com/2009/12/solaris-under-qemu-how-to.html#uds-search-results
>>
>> compi
On 11/29/2011 10:51 PM, Jordan Justen wrote:
> > One way to verify is to to 'info qdev' and 'info mtree' with qemu-1.0
> > and qemu-1.1 -M pc-1.0, and see that you get the same results.
>
> I think this means that I cannot add a pc-sysfw qdev for pc-1.0.
> (Even if the rom memory usage matches pc-1
On Thu, Dec 01, 2011 at 11:41:52AM +0200, Avi Kivity wrote:
> On 12/01/2011 11:37 AM, Gleb Natapov wrote:
> > >
> > > Looks reasonable. Should go into 1.1. Should we backport it to
> > > 1.0.blah? From 95c318f's description, it doesn't happen in normal
> > > circumstances.
> > >
> > To reprodu
On 12/01/2011 11:47 AM, Gleb Natapov wrote:
> On Thu, Dec 01, 2011 at 11:41:52AM +0200, Avi Kivity wrote:
> > On 12/01/2011 11:37 AM, Gleb Natapov wrote:
> > > >
> > > > Looks reasonable. Should go into 1.1. Should we backport it to
> > > > 1.0.blah? From 95c318f's description, it doesn't happe
On Thu, Dec 01, 2011 at 11:54:33AM +0200, Avi Kivity wrote:
> On 12/01/2011 11:47 AM, Gleb Natapov wrote:
> > On Thu, Dec 01, 2011 at 11:41:52AM +0200, Avi Kivity wrote:
> > > On 12/01/2011 11:37 AM, Gleb Natapov wrote:
> > > > >
> > > > > Looks reasonable. Should go into 1.1. Should we backport
Thank you for subscribing. You have now unsubscribed and no more messages will
be sent.
On 1 December 2011 09:03, 陳韋任 wrote:
> I read the thread talking about the broken tb_unlink [1], and I'm surprised
> that tb_unlink is broken even under single-threaded mode and system mode. You
> mentioned (b) could be the IO thread in [1]. I think we don't enable IO thread
> in system mode righ
On Thu, Dec 01, 2011 at 06:49:54PM +1300, Alexey Korolev wrote:
> Isaku san,
>
> I've just added you to discussion.
> There are some issues with PCI 64bit support in Windows. Windows
> fails to assign the resource if it doesn't fit in first 4GB window.
>
> I really don't know why it happens.
> On
On 01.12.2011, at 04:50, 陳韋任 wrote:
> Hi Alex,
>
>> Very cool! I was thinking about this for a while myself now. It's especially
>> appealing these days since you can do the hotspot optimization in a separate
>> thread :).
>>
>> Especially in system mode, you also need to flush when tb_flush(
On Wed, Nov 30, 2011 at 03:03:35PM -0600, Anthony Liguori wrote:
> +DeviceState *qdev_resolve_path(const char *path, bool *ambiguous)
> +{
> +bool partial_path = true;
> +DeviceState *dev;
> +gchar **parts;
> +
> +parts = g_strsplit(path, "/", 0);
> +if (parts == NULL || parts[0
On Sat, Nov 26, 2011 at 9:01 AM, Blue Swirl wrote:
> On Fri, Nov 25, 2011 at 18:24, Ignacio Geli wrote:
>>
>> El 25/11/11 13:01, Andreas Färber escribió:
>>
>> Hi,
>>
>> Am 25.11.2011 16:23, schrieb Ignacio Geli:
>>
>> Im trying to run a solaris 2.5.1 vm acording the instructions of i found
>> in
> The IO thread is always enabled in QEMU these days.
We use QEMU 0.13. I think IO thread is not enabled by default.
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
On Wed, Nov 30, 2011 at 03:03:37PM -0600, Anthony Liguori wrote:
> +/**
> + * @qdev_property_add_link - Add a link property to a device
> + *
> + * Links establish relationships between devices. Links are unidirection
s/unidirection/unidirectional/
On 1 December 2011 03:50, 陳韋任 wrote:
> We use QEMU 0.13
Oops, I missed this. 0.13 is over a year old now. There is zero point
in doing any kind of engineering work of this scale on such an old
codebase. You need to be tracking the head of git master, generally,
if you want (a) any hope of getting
On Wed, Nov 30, 2011 at 03:03:40PM -0600, Anthony Liguori wrote:
> +##
> +# @qom-get:
> +#
> +# This command will get a property from a device model path and return the
> +# value.
> +#
> +# @path: The path within the device model. There are two forms of supported
> +#paths--absolute and p
On Wed, Nov 30, 2011 at 03:03:43PM -0600, Anthony Liguori wrote:
> +/* FIXME there's some major spaghetti here. Somehow we create the
> devices
> + * on the PIIX before we actually create it. We create the PIIX3 deep in
> + * the recess of the i440fx creation too and then loose the D
On 11/30/2011 11:03 PM, Anthony Liguori wrote:
> Links represent an ephemeral relationship between devices. They are meant to
> replace the qdev concept of busses by allowing more informal relationships
> between devices.
So, links are equivalent to pointers?
> Links are fairly limited in their
On Wed, Nov 30, 2011 at 03:03:45PM -0600, Anthony Liguori wrote:
> @@ -1210,6 +1210,9 @@ void qdev_property_add_child(DeviceState *dev, const
> char *name,
> qdev_property_add(dev, name, type, qdev_get_child_property,
>NULL, NULL, child, errp);
>
> +g_assert(chil
Hi,
> Ok Here are logs the faulty device is: 00:05.0.
> In the first case the BAR1 size is 512MB and it fails in Windows (Linux
> is fine, the kernel enumerates the bus and assigns the resource above 4GB),
> In the second case the BAR1 size is 256M and works fine.
> === PCI new allocation pass
On Wed, Nov 30, 2011 at 03:03:47PM -0600, Anthony Liguori wrote:
> diff --git a/QMP/qom-get b/QMP/qom-get
> new file mode 100755
> index 000..b086bc5
> --- /dev/null
> +++ b/QMP/qom-get
> @@ -0,0 +1,26 @@
> +#!/usr/bin/python
> +##
> +# Virtio Support
QEMU Object Model property getter utility
On 1 December 2011 01:37, wrote:
> Qemu based on:
> git://git.linaro.org/qemu/qemu-linaro.git
Please don't post patches to upstream which are based on qemu-linaro.
This work should be entirely doable against upstream qemu.
You don't say whether you've tested this with TCG -- done correctly
it s
On 1 December 2011 11:29, Peter Maydell wrote:
> On 1 December 2011 01:37, wrote:
>> Qemu based on:
>> git://git.linaro.org/qemu/qemu-linaro.git
>
> Please don't post patches to upstream which are based on qemu-linaro.
> This work should be entirely doable against upstream qemu.
To clarify that
On Thu, Dec 1, 2011 at 11:21 AM, Avi Kivity wrote:
> On 11/30/2011 11:03 PM, Anthony Liguori wrote:
>> Links represent an ephemeral relationship between devices. They are meant to
>> replace the qdev concept of busses by allowing more informal relationships
>> between devices.
>
> So, links are e
Hi,
>> PCI: map device bus 0, bfd 0x28
>> bar 0, addr febe, size 1 [mem]
>> bar 1, addr 0, size 2000 [mem]
>
> Somehow seabios didn't recognise the bar correctly it seems (both 512
> and 256 MB cases look the same). For the 256 MB case seabios should
> have mapped the bar @ 0xe
On 12/01/2011 01:35 PM, Stefan Hajnoczi wrote:
> >>
> >> +static void qdev_get_link_property(DeviceState *dev, Visitor *v, void
> >> *opaque,
> >> + const char *name, Error **errp)
> >> +{
> >> +DeviceState **child = opaque;
> >> +gchar *path;
> >> +
> >>
On 12/01/2011 02:19 AM, Stefan Hajnoczi wrote:
On Wed, Nov 30, 2011 at 03:03:31PM -0600, Anthony Liguori wrote:
+/**
+ * @DevicePropertyEtter - called when trying to get/set a property
An established term for this is an "accessor". I've never heard "etter"
before and it looks like a typo on f
On 12/01/2011 02:33 AM, Stefan Hajnoczi wrote:
On Wed, Nov 30, 2011 at 03:03:32PM -0600, Anthony Liguori wrote:
+static void qdev_set_legacy_property(DeviceState *dev, Visitor *v, void
*opaque,
+ const char *name, Error **errp)
+{
+Property *prop = opaque
On 12/01/2011 04:24 AM, Stefan Hajnoczi wrote:
On Wed, Nov 30, 2011 at 03:03:35PM -0600, Anthony Liguori wrote:
+DeviceState *qdev_resolve_path(const char *path, bool *ambiguous)
+{
+bool partial_path = true;
+DeviceState *dev;
+gchar **parts;
+
+parts = g_strsplit(path, "/", 0);
On 12/01/2011 05:04 AM, Stefan Hajnoczi wrote:
On Wed, Nov 30, 2011 at 03:03:40PM -0600, Anthony Liguori wrote:
+##
+# @qom-get:
+#
+# This command will get a property from a device model path and return the
+# value.
+#
+# @path: The path within the device model. There are two forms of support
On 12/01/2011 05:07 AM, Stefan Hajnoczi wrote:
On Wed, Nov 30, 2011 at 03:03:43PM -0600, Anthony Liguori wrote:
+/* FIXME there's some major spaghetti here. Somehow we create the devices
+ * on the PIIX before we actually create it. We create the PIIX3 deep in
+ * the recess of the
On 12/01/2011 05:21 AM, Stefan Hajnoczi wrote:
On Wed, Nov 30, 2011 at 03:03:45PM -0600, Anthony Liguori wrote:
@@ -1210,6 +1210,9 @@ void qdev_property_add_child(DeviceState *dev, const char
*name,
qdev_property_add(dev, name, type, qdev_get_child_property,
NULL,
On 12/01/2011 05:26 AM, Stefan Hajnoczi wrote:
On Wed, Nov 30, 2011 at 03:03:47PM -0600, Anthony Liguori wrote:
diff --git a/QMP/qom-get b/QMP/qom-get
new file mode 100755
index 000..b086bc5
--- /dev/null
+++ b/QMP/qom-get
@@ -0,0 +1,26 @@
+#!/usr/bin/python
+##
+# Virtio Support
QEMU Obje
On 12/01/2011 04:55 AM, Stefan Hajnoczi wrote:
On Wed, Nov 30, 2011 at 03:03:37PM -0600, Anthony Liguori wrote:
+/**
+ * @qdev_property_add_link - Add a link property to a device
+ *
+ * Links establish relationships between devices. Links are unidirection
s/unidirection/unidirectional/
Ack
Since we might want to test arbitrary qemu, qemu-img and
qemu-io paths, allow users to specify environment variable
values for QEMU_PROG, QEMU_IMG_PROG and QEMU_IO_PROG so
the testsuite will use those values rather than find them
on PATH. Obviously, if such env variables are not set
prior to script
Print the paths of the programs under test
(qemu, qemu-img and qemu-io).
Signed-off-by: Lucas Meneghel Rodrigues
---
check |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/check b/check
index 84ef3e5..8499a04 100755
--- a/check
+++ b/check
@@ -158,6 +158,9 @@ FULL_HOST_
In automated test environments, we often build and test
qemu from arbitrary paths, rather than installing them
on standard PATH directories. Of course, appending directories
to PATH might produce the desired result, but making it
possible to specify arbitrary qemu paths through environment
variable
On 12/01/2011 05:21 AM, Avi Kivity wrote:
On 11/30/2011 11:03 PM, Anthony Liguori wrote:
Links represent an ephemeral relationship between devices. They are meant to
replace the qdev concept of busses by allowing more informal relationships
between devices.
So, links are equivalent to pointer
On 12/01/2011 06:34 AM, Avi Kivity wrote:
On 12/01/2011 01:35 PM, Stefan Hajnoczi wrote:
+static void qdev_get_link_property(DeviceState *dev, Visitor *v, void *opaque,
+ const char *name, Error **errp)
+{
+DeviceState **child = opaque;
+gchar *path;
+
On 12/01/2011 03:47 PM, Anthony Liguori wrote:
> On 12/01/2011 06:34 AM, Avi Kivity wrote:
>> On 12/01/2011 01:35 PM, Stefan Hajnoczi wrote:
>
> +static void qdev_get_link_property(DeviceState *dev, Visitor *v,
> void *opaque,
> + const char *name,
On 12/01/2011 03:44 PM, Anthony Liguori wrote:
>> So, links are equivalent to pointers?
>
>
> Yup. Once we have qom inheritance (next stage), we can have a
> link property and you'll be able to set it to an E1000State
> with the appropriate casting and error checking taking place.
I really like t
On Thu, Dec 1, 2011 at 1:39 PM, Anthony Liguori wrote:
> On 12/01/2011 05:26 AM, Stefan Hajnoczi wrote:
>>
>> On Wed, Nov 30, 2011 at 03:03:47PM -0600, Anthony Liguori wrote:
> Ack. I made these changes actually but something got lost when I sent the
> patches out. I actually used git-publish fo
Bonjour,
des nouveaux offres emplois pour vous
http://www.universfreeads.com/emplois.php
..
On 11/30/2011 11:03 PM, Anthony Liguori wrote:
> This is a follow up to my previous series to get us started in the QOM
> direction. A few things are different this time around. Most notably:
>
> 1) Devices no longer have names. Instead, path names are always used to
> identify devices.
>
>
On 2011-11-29 22:36, Eric B Munson wrote:
> Often when a guest is stopped from the qemu console, it will report spurious
> soft lockup warnings on resume. There are kernel patches being discussed that
> will give the host the ability to tell the guest that it is being stopped and
> should ignore t
On 12/01/2011 08:20 AM, Avi Kivity wrote:
On 11/30/2011 11:03 PM, Anthony Liguori wrote:
This is a follow up to my previous series to get us started in the QOM
direction. A few things are different this time around. Most notably:
1) Devices no longer have names. Instead, path names are alw
On 12/01/2011 04:42 PM, Anthony Liguori wrote:
>
>>
>> We need good tools to allow easy review of the ABI bits hiding in
>> patches, and to maintain ABI compatibility. Something like
>> qemu-print-abi that dumps all properties for all devices. Patches could
>> show the ABI changes by including a
On 2011-10-23 17:39, Vadim Rozenfeld wrote:
> ---
> Makefile.target |2 +
> target-i386/cpuid.c | 14 ++
> target-i386/hyperv.c | 65
> ++
> target-i386/hyperv.h | 37
> 4 files changed, 118 inser
On 2011-10-23 17:39, Vadim Rozenfeld wrote:
> ---
> target-i386/kvm.c | 73 +++-
> 1 files changed, 71 insertions(+), 2 deletions(-)
>
> diff --git a/target-i386/kvm.c b/target-i386/kvm.c
> index 82fec8c..c061e3b 100644
> --- a/target-i386/kvm.c
>
On 12/01/2011 08:03 AM, Avi Kivity wrote:
On 12/01/2011 03:44 PM, Anthony Liguori wrote:
So, links are equivalent to pointers?
Yup. Once we have qom inheritance (next stage), we can have a
link property and you'll be able to set it to an E1000State
with the appropriate casting and error che
On 12/01/2011 07:50 AM, Avi Kivity wrote:
On 12/01/2011 03:47 PM, Anthony Liguori wrote:
What if it's called with the output visitor? (warning: confusing
convention).
The reason there's a single Visitor type that works for both input and
output visitors is to make it so you can write a single
On 12/01/2011 04:53 PM, Anthony Liguori wrote:
>
>> What does the client code looks like for link?
>
> I'm not sure what you mean by client code,
This:
> but consider a device called UsbController that looks like:
>
> struct UsbController
> {
> DeviceState parent;
>
> UsbDevice *slave; /
On 12/01/2011 08:48 AM, Avi Kivity wrote:
On 12/01/2011 04:42 PM, Anthony Liguori wrote:
We need good tools to allow easy review of the ABI bits hiding in
patches, and to maintain ABI compatibility. Something like
qemu-print-abi that dumps all properties for all devices. Patches could
show
Hi,
> In terms of QMP client code, you just do:
>
> qom-set /path/to/usb-controller.slave /some/other/device
Lacks notification. usb-controller doesn't notice that you have plugged
in some usb device and thus can't raise an IRQ to notify the guest ...
cheers,
Gerd
From: "Aneesh Kumar K.V"
Fsdriver callback that operate on file descriptor need to
differentiate between directory fd and file fd.
Based on the original patch from Sassan Panahinejad
Signed-off-by: Aneesh Kumar K.V
---
fsdev/file-op-9p.h |4 ++--
hw/9pfs/cofile.c |4
On 12/01/2011 09:00 AM, Avi Kivity wrote:
On 12/01/2011 04:53 PM, Anthony Liguori wrote:
What does the client code looks like for link?
I'm not sure what you mean by client code,
This:
but consider a device called UsbController that looks like:
struct UsbController
{
DeviceState
On 12/01/2011 05:03 PM, Gerd Hoffmann wrote:
> Hi,
>
> > In terms of QMP client code, you just do:
> >
> > qom-set /path/to/usb-controller.slave /some/other/device
>
> Lacks notification. usb-controller doesn't notice that you have plugged
> in some usb device and thus can't raise an IRQ to no
On 12/01/2011 09:03 AM, Gerd Hoffmann wrote:
Hi,
In terms of QMP client code, you just do:
qom-set /path/to/usb-controller.slave /some/other/device
Lacks notification. usb-controller doesn't notice that you have plugged
in some usb device and thus can't raise an IRQ to notify the guest
On 11/30/2011 07:15 AM, Takuya Yoshikawa wrote:
> (2011/11/30 14:02), Takuya Yoshikawa wrote:
>
>> IIUC, even though O(1) is O(1) at the timing of GET DIRTY LOG, it
>> needs O(N) write
>> protections with respect to the total number of dirty pages:
>> distributed, but
>> actually each page fault, w
On Wed, 30 Nov 2011, Stefan Weil wrote:
> It's common to use either out-of-tree builds or in-tree builds,
> but not to mix both variants with a common root directory.
> I think QEMU should explicitly forbid that mixed scenario (like
> other projects do).
>
> Even with your fix there can remain pro
Hi,
> +static void rtc_get_date(DeviceState *dev, Visitor *v, void *opaque,
> + const char *name, Error **errp)
> +{
> +ISADevice *isa = DO_UPCAST(ISADevice, qdev, dev);
> +RTCState *s = DO_UPCAST(RTCState, dev, isa);
> +
> +visit_start_struct(v, NULL, "struct
Am 30.11.2011 22:03, schrieb Anthony Liguori:
> qdev properties are settable only during construction and static to classes.
> This isn't flexible enough for QOM.
>
> This patch introduces a property interface for qdev that provides dynamic
> properties that are tied to objects, instead of classes
Hi,
> +for (prop = dev->info->props; prop && prop->name; prop++) {
> +qdev_property_add_legacy(dev, prop, NULL);
> +}
bus properties?
> +static void qdev_get_legacy_property(DeviceState *dev, Visitor *v, void
> *opaque,
> + const char *name,
On 12/01/2011 09:19 AM, Stefano Stabellini wrote:
On Wed, 30 Nov 2011, Stefan Weil wrote:
It's common to use either out-of-tree builds or in-tree builds,
but not to mix both variants with a common root directory.
I think QEMU should explicitly forbid that mixed scenario (like
other projects do).
Am 30.11.2011 22:03, schrieb Anthony Liguori:
> Expose all legacy properties through the new QOM property mechanism. The qdev
> property types are exposed through the 'legacy<>' namespace. They are always
> visited as strings since they do their own string parsing.
>
> Signed-off-by: Anthony Lig
> Hi
Hi Juan,
Sorry for taking so long to reply -- my email filters apparently
aren't setup correctly!
> Do you have any performance number for this? And examples on how your
> are using it?
The performance should depend only on the VMA backing the file, in
addition to any indirect overhead ca
On 30 November 2011 03:36, Peter Chubb wrote:
Commit messages should be formatted with a short summary line,
then a blank line, then a more detailed description. You've
put everything into one extremely long summary line here, which
looks odd in git log. Try:
===begin===
hw/imx_serial: Implement
On 1 December 2011 16:55, Peter Maydell wrote:
> On 30 November 2011 03:36, Peter Chubb wrote:
>> Signed-off-by: Hans Jang
Is this email address correct? Trying to send this email got me:
550 550 ... User not known (state 17).
>> Signed-off-by: Adam Clench
>> Signed-off-by: Peter Chubb
--
Signed-off-by: Benoît Canet
---
hw/ppc_prep.c | 80 -
1 files changed, 62 insertions(+), 18 deletions(-)
diff --git a/hw/ppc_prep.c b/hw/ppc_prep.c
index f22d5b9..299305b 100644
--- a/hw/ppc_prep.c
+++ b/hw/ppc_prep.c
@@ -94,7 +94,8 @@ st
Signed-off-by: Benoît Canet
---
hw/applesmc.c | 20
1 files changed, 12 insertions(+), 8 deletions(-)
diff --git a/hw/applesmc.c b/hw/applesmc.c
index c47b592..fb11bdf 100644
--- a/hw/applesmc.c
+++ b/hw/applesmc.c
@@ -165,6 +165,16 @@ static uint32_t applesmc_io_cmd_readb
These patches convert two files ioports to memory API.
Benoît Canet (2):
applesmc: convert portio to memory API
ppc_prep: convert ioport to memory API
hw/applesmc.c | 20 -
hw/ppc_prep.c | 80 -
2 files changed, 74 inser
On 30 November 2011 03:36, Peter Chubb wrote:
>
> Signed-off-by: Hans Jang
> Signed-off-by: Adam Clench
> Signed-off-by: Peter Chubb
> ---
> Makefile.target | 2
> hw/imx_timer.c | 460
>
> 2 files changed, 461 insertions(+), 1 del
When you do "cpu_set online" where > current number of cpus,
qemu-kvm will end up crashing when qdev finds hotplug is not enabled.
Let's instead gracefully refuse.
See https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/878422 for
the related bug report.
Signed-off-by: Serge Hallyn
---
hw/
The qed-tool.py utility can inspect and manipulate QED image files. It
can be used for testing to see the state of image metadata and also to
inject corruptions into the image file. It also has a scrubbing feature
to copy just the metadata out of an image file, allowing users to share
broken imag
Am 01.12.2011 11:06, schrieb Gleb Natapov:
> On Thu, Dec 01, 2011 at 11:54:33AM +0200, Avi Kivity wrote:
>> On 12/01/2011 11:47 AM, Gleb Natapov wrote:
>>> On Thu, Dec 01, 2011 at 11:41:52AM +0200, Avi Kivity wrote:
On 12/01/2011 11:37 AM, Gleb Natapov wrote:
>>
>> Looks reasonable. S
On Thu, 01 Dec 2011, Jan Kiszka wrote:
> On 2011-11-29 22:36, Eric B Munson wrote:
> > Often when a guest is stopped from the qemu console, it will report spurious
> > soft lockup warnings on resume. There are kernel patches being discussed
> > that
> > will give the host the ability to tell the
On Thu, 01 Dec 2011, Jan Kiszka wrote:
> On 2011-11-29 22:36, Eric B Munson wrote:
> > Often when a guest is stopped from the qemu console, it will report spurious
> > soft lockup warnings on resume. There are kernel patches being discussed
> > that
> > will give the host the ability to tell the
On 12/01/2011 07:18 PM, Andreas Färber wrote:
> Am 01.12.2011 11:06, schrieb Gleb Natapov:
> > On Thu, Dec 01, 2011 at 11:54:33AM +0200, Avi Kivity wrote:
> >> On 12/01/2011 11:47 AM, Gleb Natapov wrote:
> >>> On Thu, Dec 01, 2011 at 11:41:52AM +0200, Avi Kivity wrote:
> On 12/01/2011 11:37 AM
On Wed, Nov 30, 2011 at 06:41:13PM +0100, Andrea Arcangeli wrote:
> On Wed, Nov 30, 2011 at 09:52:37PM +0530, Dipankar Sarma wrote:
> > create the guest topology correctly and optimize for NUMA. This
> > would work for us.
>
> Even on the case of 1 guest that fits in one node, you're not going to
On 30 November 2011 03:36, Peter Chubb wrote:
> Signed-off-by: Hans Jang
> Signed-off-by: Adam Clench
> Signed-off-by: Peter Chubb
> ---
> Makefile.target | 2
> hw/imx_avic.c | 378
>
> 2 files changed, 379 insertions(+), 1 delet
Often when a guest is stopped from the qemu console, it will report spurious
soft lockup warnings on resume. There are kernel patches being discussed that
will give the host the ability to tell the guest that it is being stopped and
should ignore the soft lockup warning that generates. This patch
On 2011-12-01 18:19, Eric B Munson wrote:
> On Thu, 01 Dec 2011, Jan Kiszka wrote:
>
>> On 2011-11-29 22:36, Eric B Munson wrote:
>>> Often when a guest is stopped from the qemu console, it will
>>> report spurious soft lockup warnings on resume. There are
>>> kernel patches being discussed that
On 2011-12-01 18:31, Arend van Spriel wrote:
> On 12/01/2011 06:19 PM, Eric B Munson wrote:
>> On Thu, 01 Dec 2011, Jan Kiszka wrote:
>>
>>> On 2011-11-29 22:36, Eric B Munson wrote:
+
static void cpu_update_state(void *opaque, int running, RunState state)
{
CPUState *env
On 2011-12-01 18:22, Eric B Munson wrote:
> On Thu, 01 Dec 2011, Jan Kiszka wrote:
>
>> On 2011-11-29 22:36, Eric B Munson wrote:
>>> Often when a guest is stopped from the qemu console, it will report spurious
>>> soft lockup warnings on resume. There are kernel patches being discussed
>>> that
On Thu, Dec 01, 2011 at 10:55:20PM +0530, Dipankar Sarma wrote:
> On Wed, Nov 30, 2011 at 06:41:13PM +0100, Andrea Arcangeli wrote:
> > On Wed, Nov 30, 2011 at 09:52:37PM +0530, Dipankar Sarma wrote:
> > > create the guest topology correctly and optimize for NUMA. This
> > > would work for us.
> >
1 - 100 of 147 matches
Mail list logo
