Qemu goes into inconsistent state when Cortex M3 systick timer in setup and
enabled.
http://forums.arm.com/index.php?/topic/15159-systick-timer-of-cortex-m3-in-qemu-not-working/
Arunkumar V
On Fri, Aug 26, 2011 at 09:22:45AM +0300, Sasha Levin wrote:
> On Thu, 2011-08-25 at 16:25 +, Decker, Schorschi wrote:
> > 2) implement the feature as an agent in the guest OS where the
> > hypervisor can only query the guest OS agent, using a standard TCP/IP
> > methodology.
>
> I was planning
On Thu, Aug 25, 2011 at 04:48:36PM -0500, Anthony Liguori wrote:
> One would be exposing a well supported device (like IDE emulation)
> and having a magic mode that allowed you to basically promote the
> device from IDE emulation to virtio-blk. Likewise, you could do
> something like that to promo
On Fri, Aug 26, 2011 at 09:08:02AM +0300, Sasha Levin wrote:
> You're thinking about trying to expose all interfaces during boot and
> seeing which ones the kernel bites?
No, that's a bad idea. A current guest would register that as two
disks. It might even try to write to them independently.
Y
Technically the new mmapped pages are already initialized to zero
since they are anonymous, however we have to take care with the
contents that come from the remaining part of the previous page: it
may contains garbage data due to a previous heap usage (grown then
shrunken).
This patch completes c
On 08/26/2011 05:51 AM, Peter Maydell wrote:
Don't you need some magic around helper calls that read/write
the time to keep -icount working? I don't understand this but
Paolo does...
Let's say I understand the theory (how icount relies on it) more than
the practice (how the targets should do i
Remove PROVIDE_HIDDEN and ONLY_IF_{RO,RW} from linker scripts to make
them work with older binutils versions. Fixes *-bsd-user build on
OpenBSD 4.9 which ships binutils 2.15.
Signed-off-by: Gerd Hoffmann
---
arm.ld| 12 ++--
hppa.ld | 18 --
i386.ld |8 ++
On Fri, Aug 26, 2011 at 12:24:23AM -0400, David Gibson wrote:
> On Thu, Aug 25, 2011 at 08:25:45AM -0500, Alexander Graf wrote:
> > On 25.08.2011, at 07:31, Roedel, Joerg wrote:
> > > For mmio we could stop the guest and replace the mmio region with a
> > > region that is filled with 0xff, no?
> >
The original charm of traditional Chinese medicine lies in the following free and unique services:1 TCM Diagnosis Just a health list and a photo of the tongue coating needed, the expert of traditional Chinese medicine would make a professional diagnosis. Why not have a try?2 Health Plan A customiz
On Fri, Aug 26, 2011 at 12:20:00AM -0400, David Gibson wrote:
> On Wed, Aug 24, 2011 at 01:03:32PM +0200, Roedel, Joerg wrote:
> > On Wed, Aug 24, 2011 at 05:33:00AM -0400, David Gibson wrote:
> > > On Wed, Aug 24, 2011 at 11:14:26AM +0200, Roedel, Joerg wrote:
> >
> > > > I don't see a reason to
On Thu, Aug 18, 2011 at 08:15:43AM -0700, Avi Kivity wrote:
> It's correct but insufficient, the filtering code
> (pci_bridge_filter) needs to be updated to use the memory API.
>
> Basically it gets simpler and correcter.
I've been struggling with the following problem: bridges have two memory
ra
On 08/19/11 19:08, Alon Levy wrote:
Fix the ticket expiration on target vm for a spice connection without
introducing
a race between the spice server switching the client to the new host itself and
the target libvirt setting the new expiration date, by adding an option to
client_migrate_info to
On Mon, Aug 15, 2011 at 5:38 PM, Bob Breuer wrote:
> Mark Cave-Ayland wrote:
>> On 11/08/11 17:11, Bob Breuer wrote:
>>
>>> The ledma base address defaults to 0xff00 on reset. This
>>> fixes a bug with Solaris and SS-20 OBP when boot net is skipped.
>>>
>>> Signed-off-by: Bob Breuer
>>> ---
>
On Thu, Aug 18, 2011 at 11:22:31AM +0800, Wen Congyang wrote:
> >From 3cee5a14f0ff7aeac148f9416eac6fa7c6ca Mon Sep 17 00:00:00 2001
> From: Wen Congyang
> Date: Thu, 18 Aug 2011 09:33:19 +0800
> Subject: [PATCH] PCI_Bridge: use parent bus's address space
>
> The pci device may call pci_regist
On Fri, Aug 26, 2011 at 11:54:49AM +0200, Gerd Hoffmann wrote:
> On 08/19/11 19:08, Alon Levy wrote:
> >Fix the ticket expiration on target vm for a spice connection without
> >introducing
> >a race between the spice server switching the client to the new host itself
> >and
> >the target libvirt
The following changes since commit e8906f3529a452276375ab8e7b8598751bc33b01:
PPC: E500: Set ESR values (2011-08-23 22:24:40 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git for_anthony
Isaku Yamahata (2):
pcie/slot: fix hotplug e
... to make vmstate id string truely unique with multiple host
controllers, i.e. move from "1/usb-ptr" to ":00:01.3/1/usb-ptr"
(usb tabled connected to piix3 uhci).
Obvious problem with that is that it breaks migration from and to older
versions, thats why it is RfC. I don't see any way to fi
On 08/26/11 12:03, Daniel P. Berrange wrote:
On Fri, Aug 26, 2011 at 11:54:49AM +0200, Gerd Hoffmann wrote:
On 08/19/11 19:08, Alon Levy wrote:
Fix the ticket expiration on target vm for a spice connection without
introducing
a race between the spice server switching the client to the new host
On Fri, 2011-08-26 at 09:04 +0100, Richard W.M. Jones wrote:
> On Fri, Aug 26, 2011 at 09:22:45AM +0300, Sasha Levin wrote:
> > On Thu, 2011-08-25 at 16:25 +, Decker, Schorschi wrote:
> > > 2) implement the feature as an agent in the guest OS where the
> > > hypervisor can only query the guest
On 25 August 2011 14:13, Daniel P. Berrange wrote:
> On Thu, Aug 25, 2011 at 01:27:00PM +0100, Peter Maydell wrote:
>> Does this constitute a change in the required version of gnutls which
>> we need to document in the proto-changelog for the next release?
>> Is it worth updating the configure tls
On Fri, Aug 26, 2011 at 12:11:20PM +0200, Gerd Hoffmann wrote:
> ... to make vmstate id string truely unique with multiple host
> controllers, i.e. move from "1/usb-ptr" to ":00:01.3/1/usb-ptr"
> (usb tabled connected to piix3 uhci).
>
> Obvious problem with that is that it breaks migration fr
On Fri, Aug 26, 2011 at 11:03:38AM +0100, Daniel P. Berrange wrote:
> On Fri, Aug 26, 2011 at 11:54:49AM +0200, Gerd Hoffmann wrote:
> > On 08/19/11 19:08, Alon Levy wrote:
> > >Fix the ticket expiration on target vm for a spice connection without
> > >introducing
> > >a race between the spice ser
Hi.
checkpatch.pl correctly reports a warning for the following code:
if (something)
foo;
else
bar;
WARNING: braces {} are necessary for all arms of this statement
#1: FILE: tmp/a.c:1:
+if (something)
[...]
+else
[...]
But if I modify it as follows, checkpatch.pl doesn't report any
w
On Fri, Aug 26, 2011 at 01:18:49PM +0300, Sasha Levin wrote:
> On Fri, 2011-08-26 at 09:04 +0100, Richard W.M. Jones wrote:
> > On Fri, Aug 26, 2011 at 09:22:45AM +0300, Sasha Levin wrote:
> > > On Thu, 2011-08-25 at 16:25 +, Decker, Schorschi wrote:
> > > > 2) implement the feature as an agent
Hi,
[you would replace docs/ich9-ehci-uhci.cfg with e.g.
/usr/local/share/doc/qemu/docs/ich9-ehci-uhci.cfg, but turns out
ehci seems broken for me here with FreeBSD guests at least, I get:
FETCHENTRY: entry at 22C5484 is of type 2 which is not supported yet
processing error
On Fri, Aug 26, 2011 at 12:17:58PM +0200, Gerd Hoffmann wrote:
> On 08/26/11 12:03, Daniel P. Berrange wrote:
> >On Fri, Aug 26, 2011 at 11:54:49AM +0200, Gerd Hoffmann wrote:
> >>On 08/19/11 19:08, Alon Levy wrote:
> >>>Fix the ticket expiration on target vm for a spice connection without
> >>>in
On 08/26/11 12:25, Daniel P. Berrange wrote:
On Fri, Aug 26, 2011 at 12:11:20PM +0200, Gerd Hoffmann wrote:
... to make vmstate id string truely unique with multiple host
controllers, i.e. move from "1/usb-ptr" to ":00:01.3/1/usb-ptr"
(usb tabled connected to piix3 uhci).
Obvious problem wi
From: "Daniel P. Berrange"
There are two common cases where migrate_cancel is intended to be
used
1. When migration is not converging due to an overactive
guest and insufficient network bandwidth
2. When migration is stuck due a network outage, waiting
for the TCP transmit timeout
Hi,
Ok, so I think we should be able to fix the race outlined above
without adding new monitor commands, just by letting libvirt set the
spice ticket in stage 2.
Is that different then what I suggested in my reply to Daniel's 5 stage outline?
I think we have to care to not mix up switch-ho
On Fri, Aug 26, 2011 at 01:00:29PM +0200, Gerd Hoffmann wrote:
> Hi,
>
> >>Ok, so I think we should be able to fix the race outlined above
> >>without adding new monitor commands, just by letting libvirt set the
> >>spice ticket in stage 2.
> >
> >Is that different then what I suggested in my re
On Fri, Aug 26, 2011 at 11:59:28AM +0100, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> There are two common cases where migrate_cancel is intended to be
> used
>
> 1. When migration is not converging due to an overactive
> guest and insufficient network bandwidth
> 2. When
Hi,
/me wonders what FreeBSD tries to do here? This triggers even without a
single device connected and I can't think of a reason to use a siTD in
that case ...
Ah, the siTD simply isn't active so we can just skip it.
That is easy to do ;)
cheers,
Gerd
(1) libvirt sets spice ticket at dst (stage 2)
(2) migration src->dst (stage 3)
(3) spice client switches connection to dst
This is actually what we have already. The problem is that
the 'migration src->dst' here can take an arbitrary amount
of time. So by the time the spice client swit
This patch adds code to do minimal siTD handling, which is basically
just following the next pointer. This is good enougth to handle the
inactive siTDs used by FreeBSD. Active siTDs are skipped too as we
don't have split transfer support in qemu, additionally a warning is
printed.
Signed-off-by:
On Fri, Aug 26, 2011 at 11:24 AM, Peter Maydell
wrote:
> On 25 August 2011 14:13, Daniel P. Berrange wrote:
>> On Thu, Aug 25, 2011 at 01:27:00PM +0100, Peter Maydell wrote:
>>> Does this constitute a change in the required version of gnutls which
>>> we need to document in the proto-changelog fo
On Fri, Aug 26, 2011 at 11:28 AM, Pavel Borzenkov
wrote:
> checkpatch.pl correctly reports a warning for the following code:
>
> if (something)
> foo;
> else
> bar;
>
> WARNING: braces {} are necessary for all arms of this statement
> #1: FILE: tmp/a.c:1:
> +if (something)
> [...]
> +else
>
Am 25.08.2011 08:26, schrieb Christoph Hellwig:
> Account the total latency for read/write/flush requests. This allows
> management tools to average it based on a snapshot of the nr ops
> counters and allow checking for SLAs or provide statistics.
>
> Signed-off-by: Christoph Hellwig
>
> Index:
Hello everybody,
is there another way to pass the SPICE x509 private key passphrase to
qemu that is not sending it in clear via the command line?
Thanks,
Andrea
On Fri, Aug 26, 2011 at 02:39:59PM +0200, Gerd Hoffmann wrote:
> >> (1) libvirt sets spice ticket at dst (stage 2)
> >> (2) migration src->dst (stage 3)
> >> (3) spice client switches connection to dst
> >
> >This is actually what we have already. The problem is that
> >the 'migration src->ds
checkpatch.pl doesn't report warning for if/else statements with missing
'else' braces:
if (something) {
foo;
} else
bar;
The patch has been tested using the last 100 commits.
Signed-off-by: Pavel Borzenkov
---
scripts/checkpatch.pl |2 +-
1 files changed, 1 insertions(+), 1 deleti
On 08/26/2011 01:25 PM, Daniel P. Berrange wrote:
diff --git a/migration.c b/migration.c
index f5959b4..6448d0b 100644
--- a/migration.c
+++ b/migration.c
@@ -319,6 +319,11 @@ ssize_t migrate_fd_put_buffer(void *opaque, const void
*data, size_t size)
FdMigrationState *s = opaque;
ssi
On 26.08.2011, at 04:33, Roedel, Joerg wrote:
> On Fri, Aug 26, 2011 at 12:20:00AM -0400, David Gibson wrote:
>> On Wed, Aug 24, 2011 at 01:03:32PM +0200, Roedel, Joerg wrote:
>>> On Wed, Aug 24, 2011 at 05:33:00AM -0400, David Gibson wrote:
On Wed, Aug 24, 2011 at 11:14:26AM +0200, Roedel,
Hi Jan Kiszka & Blue Swirl,
Hi would like to report a strange behaviour exposed by commit 0d101938
"tcg: Reload local variables after return from longjmp" (found with
`git bisect` and then reverted to be sure).
When emulating in *user-mode* the program `msgmerge`, I get the
following error(s):
On 26 August 2011 15:15, wrote:
> Hi Jan Kiszka & Blue Swirl,
>
> Hi would like to report a strange behaviour exposed by commit 0d101938
> "tcg: Reload local variables after return from longjmp" (found with
> `git bisect` and then reverted to be sure).
>
> When emulating in *user-mode* the progra
Hi all,
I just want to do a very simple task. I'm using QEMU for debugging a new OS
and I see that there is a memory region that is being updated by an unknown
task. I don't know if it's another process or the kernel itself.
So I would like to put a physical memory watchpoint. I don't know how to
On Fri, Aug 26, 2011 at 04:19:26PM +0200, Peter Maydell wrote:
> Yes; we've discussed this before in this thread:
> http://lists.nongnu.org/archive/html/qemu-devel/2011-08/msg01623.html
>
> That commit breaks multi-threaded usermode programs (well, even
> more than they usually are). I think we de
On 2011-08-26 16:21, Zeus Gómez Marmolejo wrote:
> Hi all,
>
> I just want to do a very simple task. I'm using QEMU for debugging a new OS
> and I see that there is a memory region that is being updated by an unknown
> task. I don't know if it's another process or the kernel itself.
>
> So I woul
More than one year ago I posted some patches to add a monitor command
callend device_show. The purpose of that command is to dump the state of
some qdev device based on its vmstate.
To improve the usability of that interface, the previous series also
tried to create a canonical qdev tree path name
This simply forwards the result of the internal vsnprintf to the callers
of monitor_printf and monitor_vprintf. When invoked over a QMP session
or in absence of an active monitor, -1 is returned.
CC: Luiz Capitulino
Signed-off-by: Jan Kiszka
---
monitor.c | 23 +++
monit
This introduces device_show, a monitor command that saves the vmstate of
a qdev device and visualizes it. Buffers are cut after 16 byte by
default, but the full content can be requested via '-f'. To pretty-print
sub-arrays, vmstate is extended to store the start index name. A new
qerror is introduc
Will be used by QBuffer.
CC: Luiz Capitulino
Signed-off-by: Jan Kiszka
---
Makefile.objs |2 +-
base64.c | 202 +
base64.h | 19 ++
3 files changed, 222 insertions(+), 1 deletions(-)
create mode 100644 base64.c
creat
In order to address devices for that the user forgot or is even unable
(no_user) to provide an ID, assign an automatically generated one. Such
IDs have the format #, thus are outside the name space availing
to users. Don't use them for bus naming to avoid any other user-visible
change.
CC: Markus
On 26 August 2011 15:48, Jan Kiszka wrote:
> Will be used by QBuffer.
Is it possible to use the glib base64 encode/decode routines instead
of rolling our own here?
-- PMM
This reserves JSON objects that contain the key '__class__' for QMP-specific
complex objects. First user will be the buffer class.
CC: Luiz Capitulino
Signed-off-by: Jan Kiszka
---
QMP/qmp-spec.txt | 16 +---
1 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/QMP/qmp-
On 2011-08-26 17:21, Peter Maydell wrote:
> On 26 August 2011 15:48, Jan Kiszka wrote:
>> Will be used by QBuffer.
>
> Is it possible to use the glib base64 encode/decode routines instead
> of rolling our own here?
Yeah, times are changing. Need to check what's there and how to use it.
Jan
--
On Fri, Aug 26, 2011 at 09:07:35AM -0500, Alexander Graf wrote:
> On 26.08.2011, at 04:33, Roedel, Joerg wrote:
> >
> > The reason is that you mean the usability for the programmer and I mean
> > it for the actual user of qemu :)
>
> No, we mean the actual user of qemu. The reason being that maki
This introduces a buffer object for use with QMP. As a buffer is not
natively encodable in JSON, we encode it as a base64 string and
encapsulate the result in the new QMP object class "buffer".
The first use case for this is pushing the content of buffers that are
part of a device state into a qdi
On 26.08.2011, at 10:24, Joerg Roedel wrote:
> On Fri, Aug 26, 2011 at 09:07:35AM -0500, Alexander Graf wrote:
>> On 26.08.2011, at 04:33, Roedel, Joerg wrote:
>>>
>>> The reason is that you mean the usability for the programmer and I mean
>>> it for the actual user of qemu :)
>>
>> No, we mean
USB Devices can have up to 15 IN and 15 OUT endpoints, not 15 endpoints
total. Move from one array to two arrays (one IN, one OUT) to maintain
the endpoint state.
Note for testers: all usb fixes posted yesterday and today are
available here for your convinience:
git://git.kraxel.org/qemu usb.2
On 2011-08-26 17:23, Jan Kiszka wrote:
> On 2011-08-26 17:21, Peter Maydell wrote:
>> On 26 August 2011 15:48, Jan Kiszka wrote:
>>> Will be used by QBuffer.
>>
>> Is it possible to use the glib base64 encode/decode routines instead
>> of rolling our own here?
>
> Yeah, times are changing. Need t
By default, require 4k of consecutive zero bytes for qemu-img to make the
output file sparse by not issuing a write request for the zeroed parts. Add an
-S option to allow users to tune this setting.
This helps to avoid situations where a lot of zero sectors and data sectors are
mixed and qemu-img
On Fri, Aug 26, 2011 at 03:05:06PM +0200, Kevin Wolf wrote:
> The order of READ vs. WRITE is wrong here, so read latencies show up as
> wr_total_time. I can fix it locally if you agree that swapping the two
> lines is the right fix.
Yes, it got mixed up in one of the revamps.
On 08/25/2011 11:07 PM, Paolo Bonzini wrote:
> On 08/26/2011 05:51 AM, Peter Maydell wrote:
>> Don't you need some magic around helper calls that read/write
>> the time to keep -icount working? I don't understand this but
>> Paolo does...
>
> Let's say I understand the theory (how icount relies on
On 26 August 2011 17:28, Richard Henderson wrote:
> On 08/25/2011 11:07 PM, Paolo Bonzini wrote:
>> On 08/26/2011 05:51 AM, Peter Maydell wrote:
>>> Don't you need some magic around helper calls that read/write
>>> the time to keep -icount working? I don't understand this but
>>> Paolo does...
>>
Hi all,
current master has some qregressions:
# ./check-qdict
Running suite(s): QDict test-suite
93%: Checks: 16, Failures: 1, Errors: 0
check-qdict.c:289:F:Stress Test:qdict_stress_test:0: Assertion 'test_file !=
NULL' failed
# ./check-qjson
Running suite(s): QJSON test-suite
95%: Checks: 21
I am working on a project for which I'd like to gather statistics about
register usage. (For example, distributions of degree-of-use and dynamic
lifetimes of register-values.) Is QEMU a good tool for doing this kind of
work? Has anyone else done this? I looked at the tracing available in QEM
Hi,
I'm running Qemu-kvm hyper visor , and now I want test the serial port
-/dev/ttyS0 , .
How to check this from qemu command ..?
becoz I started VM on this hypervisor and not able to access the
/dev/ttyS0 from the VM .
Pls help
2011/8/26 Jan Kiszka :
> On 2011-08-26 16:21, Zeus Gómez Marmolejo wrote:
>> Hi all,
>>
>> I just want to do a very simple task. I'm using QEMU for debugging a new OS
>> and I see that there is a memory region that is being updated by an unknown
>> task. I don't know if it's another process or the
Benjamin Ylvisaker writes:
> I am working on a project for which I'd like to gather statistics
> about register usage. (For example, distributions of degree-of-use
> and dynamic lifetimes of register-values.) Is QEMU a good tool for
> doing this kind of work? Has anyone else done this? I looke
On Fri, Aug 26, 2011 at 2:28 PM, wrote:
> On Fri, Aug 26, 2011 at 04:19:26PM +0200, Peter Maydell wrote:
>> Yes; we've discussed this before in this thread:
>> http://lists.nongnu.org/archive/html/qemu-devel/2011-08/msg01623.html
>>
>> That commit breaks multi-threaded usermode programs (well, ev
I don't think too much has changed since the previous email went out,
but it seems like a good idea to post a summary in case there were
suggestions or objections that I missed.
VFIO v2 will rely on the platform iommu driver reporting grouping
information. Again, a group is a set of devices for
On Fri, 26 Aug 2011 18:48:52 +0200
Jan Kiszka wrote:
> Hi all,
>
> current master has some qregressions:
>
> # ./check-qdict
> Running suite(s): QDict test-suite
> 93%: Checks: 16, Failures: 1, Errors: 0
> check-qdict.c:289:F:Stress Test:qdict_stress_test:0: Assertion 'test_file !=
> NULL' fa
On 26 August 2011 18:35, Lluís wrote:
> Benjamin Ylvisaker writes:
>> I am working on a project for which I'd like to gather statistics
>> about register usage. (For example, distributions of degree-of-use
>> and dynamic lifetimes of register-values.) Is QEMU a good tool for
>> doing this kind o
On 2011-08-26 19:43, Luiz Capitulino wrote:
> On Fri, 26 Aug 2011 18:48:52 +0200
> Jan Kiszka wrote:
>
>> Hi all,
>>
>> current master has some qregressions:
>>
>> # ./check-qdict
>> Running suite(s): QDict test-suite
>> 93%: Checks: 16, Failures: 1, Errors: 0
>> check-qdict.c:289:F:Stress Test:
On 8/26/11 7:07 AM, "Alexander Graf" wrote:
>
>
> Forget the KVM case for a moment and think of a user space device driver. I as
> a user am not root. But I as a user when having access to /dev/vfioX want to
> be able to access the device and manage it - and only it. The admin of that
> box
On 2011-08-26 19:34, Blue Swirl wrote:
> 2011/8/26 Jan Kiszka :
>> On 2011-08-26 16:21, Zeus Gómez Marmolejo wrote:
>>> Hi all,
>>>
>>> I just want to do a very simple task. I'm using QEMU for debugging a new OS
>>> and I see that there is a memory region that is being updated by an unknown
>>> tas
On Fri, 26 Aug 2011 19:52:11 +0200
Jan Kiszka wrote:
> On 2011-08-26 19:43, Luiz Capitulino wrote:
> > On Fri, 26 Aug 2011 18:48:52 +0200
> > Jan Kiszka wrote:
> >
> >> Hi all,
> >>
> >> current master has some qregressions:
> >>
> >> # ./check-qdict
> >> Running suite(s): QDict test-suite
> >
On Fri, 26 Aug 2011 14:58:15 -0300
Luiz Capitulino wrote:
> On Fri, 26 Aug 2011 19:52:11 +0200
> Jan Kiszka wrote:
>
> > On 2011-08-26 19:43, Luiz Capitulino wrote:
> > > On Fri, 26 Aug 2011 18:48:52 +0200
> > > Jan Kiszka wrote:
> > >
> > >> Hi all,
> > >>
> > >> current master has some qreg
2011/8/26 Jan Kiszka :
> On 2011-08-26 19:34, Blue Swirl wrote:
>> 2011/8/26 Jan Kiszka :
>>> On 2011-08-26 16:21, Zeus Gómez Marmolejo wrote:
Hi all,
I just want to do a very simple task. I'm using QEMU for debugging a new OS
and I see that there is a memory region that is bein
On 2011-08-26 17:47, Jan Kiszka wrote:
> On 2011-08-26 17:23, Jan Kiszka wrote:
>> On 2011-08-26 17:21, Peter Maydell wrote:
>>> On 26 August 2011 15:48, Jan Kiszka wrote:
Will be used by QBuffer.
>>>
>>> Is it possible to use the glib base64 encode/decode routines instead
>>> of rolling our
On Thu, 2011-08-25 at 20:05 +0200, Joerg Roedel wrote:
> On Thu, Aug 25, 2011 at 11:20:30AM -0600, Alex Williamson wrote:
> > On Thu, 2011-08-25 at 12:54 +0200, Roedel, Joerg wrote:
>
> > > We need to solve this differently. ARM is starting to use the iommu-api
> > > too and this definitly does no
On 2011-08-26 20:02, Blue Swirl wrote:
> 2011/8/26 Jan Kiszka :
>> On 2011-08-26 19:34, Blue Swirl wrote:
>>> 2011/8/26 Jan Kiszka :
On 2011-08-26 16:21, Zeus Gómez Marmolejo wrote:
> Hi all,
>
> I just want to do a very simple task. I'm using QEMU for debugging a new
> OS
>>>
This introduces a buffer object for use with QMP. As a buffer is not
natively encodable in JSON, we encode it as a base64 string and
encapsulate the result in the new QMP object class "buffer".
The first use case for this is pushing the content of buffers that are
part of a device state into a qdi
* Michael S. Tsirkin [2011-08-25 05:11]:
> When the vhost notifier is disabled, the userspace handler runs
> immediately: virtio_pci_set_host_notifier_internal might
> call virtio_queue_notify_vq.
> Since the VQ state and the tap backend state aren't
> recovered yet, this causes
> "Guest moved use
957f1f99f263d57612807a9535f75ca4473f05f0 didn't consider
that qemu-timer-common.o is needed by simpletrace.
Fix by adding it to qga object list.
Signed-off-by: Blue Swirl
---
Makefile.objs |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Makefile.objs b/Makefile.objs
i
Avoid a crash if the guest combines FW_CFG_WRITE_CHANNEL with
a wrong value.
Signed-off-by: Blue Swirl
---
hw/fw_cfg.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
index 663ad80..8df265c 100644
--- a/hw/fw_cfg.c
+++ b/hw/fw_cfg.c
@@ -214,7
Peter Maydell writes:
> On 26 August 2011 18:35, Lluís wrote:
>> Benjamin Ylvisaker writes:
>>> I am working on a project for which I'd like to gather statistics
>>> about register usage. (For example, distributions of degree-of-use
>>> and dynamic lifetimes of register-values.) Is QEMU a good
Hello all,
I am a newbie of QEMU and wondering to know the meaning of:
if ((next_tb & 3) == 2) {
/* Instruction counter expired. */
int insns_left;
tb = (TranslationBlock *)(long)(next_tb & ~3);
/* Restore PC. */
cpu_pc_from_tb(env, tb);
insns_left = env->icount_decr.u3
Signed-off-by: Alon Levy
---
hw/pci-stub.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/pci-stub.c b/hw/pci-stub.c
index c5a0aa8..8454c30 100644
--- a/hw/pci-stub.c
+++ b/hw/pci-stub.c
@@ -1,5 +1,5 @@
/*
- * PCI stubs for plathome that doesn't support pci bus.
+ *
Blue Swirl writes:
> 957f1f99f263d57612807a9535f75ca4473f05f0 didn't consider
> that qemu-timer-common.o is needed by simpletrace.
> Fix by adding it to qga object list.
> Signed-off-by: Blue Swirl
> ---
> Makefile.objs |3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
> diff --g
Public bug reported:
See
http://comments.gmane.org/gmane.comp.emulators.qemu/18
The current configure file does not have these changes which means you
get an error when compiled under MinGW.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notifica
On Fri, 26 Aug 2011, Alon Levy wrote:
> Signed-off-by: Alon Levy
> ---
> hw/pci-stub.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/hw/pci-stub.c b/hw/pci-stub.c
> index c5a0aa8..8454c30 100644
> --- a/hw/pci-stub.c
> +++ b/hw/pci-stub.c
> @@ -1,5 +1,5 @@
> /
Signed-off-by: Hervé Poussineau
---
hw/g364fb.c | 29 +++--
trace-events |4
2 files changed, 15 insertions(+), 18 deletions(-)
diff --git a/hw/g364fb.c b/hw/g364fb.c
index b3020c5..fa074f4 100644
--- a/hw/g364fb.c
+++ b/hw/g364fb.c
@@ -21,17 +21,7 @@
#inclu
Here are some patches I have lying around since some time, which
update g364 framebuffer emulation to current Qemu standards, ie
qdev + memory + trace APIs
Please apply
Hervé Poussineau (2):
g364fb: use trace framework
g364fb: convert to qdev Extract G364 ROM contents from device
emul
* Aaron Fabbri (aafab...@cisco.com) wrote:
> On 8/26/11 7:07 AM, "Alexander Graf" wrote:
> > Forget the KVM case for a moment and think of a user space device driver. I
> > as
> > a user am not root. But I as a user when having access to /dev/vfioX want to
> > be able to access the device and man
Extract G364 ROM contents from device emulation to machine emulation,
so device emulation can be reused in other machines (Commodore Amiga)
Signed-off-by: Hervé Poussineau
---
hw/g364fb.c| 340 +---
hw/mips.h |5 -
hw/mips_jazz.c
On Fri, Aug 26, 2011 at 11:17:59PM +0400, malc wrote:
> On Fri, 26 Aug 2011, Alon Levy wrote:
>
> > Signed-off-by: Alon Levy
>
> > ---
> > hw/pci-stub.c |2 +-
> > 1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/hw/pci-stub.c b/hw/pci-stub.c
> > index c5a0aa8..8454c30
On 08/26/2011 06:36 AM, Peter Maydell wrote:
> Look at the way target-i386 and target-mips use gen_io_start()
> and gen_io_end() around x86 io insns and MIPS mtc0. I think
> that what you need is (a) to bracket with gen_io_start/end
> and (b) to end the translation block, but that's really just
> g
Add a test device which supports the kvmctl ioports,
for running the KVM test suite. This is a straight
port from the latest version of the test device present
on qemu-kvm, using the APIs currently in use by qemu.
With this we aim for daily execution of
the KVM unittests to capture any problems wi
On 08/26/2011 06:36 AM, Peter Maydell wrote:
> Look at the way target-i386 and target-mips use gen_io_start()
> and gen_io_end() around x86 io insns and MIPS mtc0. I think
> that what you need is (a) to bracket with gen_io_start/end
> and (b) to end the translation block, but that's really just
> g
1 - 100 of 108 matches
Mail list logo
