Hi Alex Williamson,
I am able (with some hacks :)) to directly assign the e1000 PCI device to KVM
guest using VFIO on Freescale device. One of the problem I am facing is about
the DMA mapping in IOMMU for PCI device BARs. On Freescale devices, the mmaped
PCI device BARs are not required to be m
On Wed, Feb 13, 2013 at 04:53:41PM +0100, Stefan Hajnoczi wrote:
> These patches report an error if negative values are given for I/O throttling
> iops or bps.
>
> Patch 1 gets do_check_io_limits() into shape so that we can add checks.
>
> Patch 2 adds the negative check.
>
> Stefan Hajnoczi (2)
On Wed, Feb 13, 2013 at 09:09:38AM +0100, Miroslav Rezanina wrote:
> This is 11th version of patch adding compare subcommand that
> compares two images. Compare has following criteria:
> - only data part is compared
> - unallocated sectors are not read
> - qemu-img returns:
> - 0 if images
Signed-off-by: Anthony Green
---
hw/moxie/Makefile.objs | 5 ++
hw/moxiesim.c | 200 +
include/sysemu/arch_init.h | 1 +
3 files changed, 206 insertions(+)
create mode 100644 hw/moxie/Makefile.objs
create mode 100644 hw/moxiesim.c
Il 14/02/2013 08:54, Antoine Mathys ha scritto:
> This patch consolidates the bit twidling involved in reading and
> writing the time registers to four functions that are used consistently.
>
> This also has the effect of fixing bug 1090558.
>
> Signed-off-by: Antoine Mathys
> ---
Nice. Do you
This patch adds the disassembler logic for moxie.
>From 57158c29b2956d03c5948b530fa476e26c893000 Mon Sep 17 00:00:00 2001
From: Anthony Green
Date: Wed, 13 Feb 2013 16:44:45 -0500
Subject: [PATCH 2/5] Add moxie disassembler
Signed-off-by: Anthony Green
---
disas.c | 6 +
disas/M
Am 13.02.2013 22:17, schrieb Blue Swirl:
> On Wed, Feb 13, 2013 at 1:22 PM, Kevin Wolf wrote:
>> Look only for clusters that start at a given physical offset.
>>
>> Signed-off-by: Kevin Wolf
>> ---
>> block/qcow2-cluster.c | 26 ++
>> 1 files changed, 18 insertions(+),
On 14 February 2013 01:47, Richard Henderson wrote:
> Version 1 merely tried to adjust bitops_flsl, here I instead eliminate
> it all from bitops.h, and standardizes on the routines from host-utils.h.
I was hoping we'd be able to get rid of host-utils.h instead,
since "Utility compute operations
[Note cc: +Laszlo, +Anthony, -qemu-trivial]
Luiz Capitulino writes:
> On Fri, 08 Feb 2013 20:34:20 +0100
> Markus Armbruster wrote:
>
>> > The real problem here is that the k, M, G suffixes, for example, are not
>> > good to be reported by QMP. So maybe we should refactor the code in a way
>> >
On 02/14/2013 10:30 AM, Paolo Bonzini wrote:
Nice. Do you have a testcase?
No, but the refactoring makes the code very easy to audit.
Please also test this patch with the two rtc-test patches at
http://thread.gmane.org/gmane.comp.emulators.qemu/188244.
I did and the tests pass.
Hello qemu maintainers,
I have been maintaining a qemu port for moxie on github for a few
years now, and would now like to submit it upstream. Moxie is a
soft-core architecture, similar to lm32 and microblaze. The GNU
toolchain has supported moxie for several years now. The qemu port is
very
On 13 February 2013 22:28, Anthony Green wrote:
> Signed-off-by: Anthony Green
> ---
[snip]
> extern const uint32_t arch_type;
> --
> 1.8.1.2
>
> [green@localhost qemu]$ cat 0005-Add-top-level-changes-for-moxie.patch
> From 43eb752f105a3c1554234acb54df4e3954d97946 Mon Sep 17 00:00:00 2001
> From
On Thu, Feb 14, 2013 at 1:56 PM, Peter Maydell wrote:
On 13 February 2013 22:28, Anthony Green wrote:
> Signed-off-by: Anthony Green
[...]
> There's something weird going on with whatever you're
> using to create these patch emails. Can you redo your next
> series in the standard '0/0 cover le
On Wed, Feb 13, 2013 at 07:49:36PM +0100, Markus Armbruster wrote:
> Hope it's not too late for -help and doc fixes.
>
> Markus Armbruster (7):
> help: Drop bogus help on -qtest and -qtest-log
> doc: Fix some option entries in qemu-doc's function index
> doc: Fill some option doc gaps in man
On Wed, Feb 13, 2013 at 03:05:28PM +0100, Kevin Wolf wrote:
> Just create lots of images and try out each of the creation options that
> qcow2 provides (except backing_file/fmt for now)
>
> I'm not totally happy with the behaviour of qemu-img in each of the
> cases, but let's be explicit and updat
Il 14/02/2013 10:45, Antoine Mathys ha scritto:
>> Nice. Do you have a testcase?
> No, but the refactoring makes the code very easy to audit.
I asked because I tried to reproduce the launchpad bug and failed.
>> Please also test this patch with the two rtc-test patches at
>> http://thread.gmane.o
Am 14.02.2013 08:55, schrieb Gleb Natapov:
> On Wed, Feb 13, 2013 at 12:43:10PM +0100, Jan Kiszka wrote:
>> Python may otherwise decide to to read larger chunks, applying the seek
>> only on the software buffer. This will return results from the wrong
>> MSRs.
>>
>> Signed-off-by: Jan Kiszka
> App
On Thu, Feb 14, 2013 at 11:51:42AM +1100, Alexey Kardashevskiy wrote:
> On 14/02/13 05:02, Laszlo Ersek wrote:
> >On 02/13/13 15:48, Alexey Kardashevskiy wrote:
> >>Hi!
> >>
> >>I am running qemu as:
> >>
> >>qemu/ppc64-softmmu/qemu-system-ppc64 -m 1024 -M pseries -trace
> >>events=trace_events -ne
On Tue, Feb 12, 2013 at 5:21 AM, Stefan Hajnoczi wrote:
> On Thu, Feb 7, 2013 at 4:19 PM, Stefan Hajnoczi wrote:
>> I believe Google will announce GSoC again this year (there is
>> no guarantee though) and I have created the wiki page so we can begin
>> organizing project ideas that students can
Hello,
Am 14.02.2013 02:06, schrieb Anthony Green:
> Hello qemu maintainers,
>
> I have been maintaining a qemu port for moxie on github for a few
> years now, and would now like to submit it upstream. Moxie is a
> soft-core architecture, similar to lm32 and microblaze. The GNU
> toolchain ha
Add support for error containment when a VFIO device assigned to a KVM
guest encounters an error. This is for PCIe devices/drivers that support AER
functionality. When the host OS is notified of an error in a device either
through the firmware first approach or through an interrupt handled by the A
- Added vfio_device_get_from_dev() as wrapper to get
reference to vfio_device from struct device.
- Added vfio_device_data() as a wrapper to get device_data from
vfio_device.
Signed-off-by: Vijay Mohan Pandarathil
---
drivers/vfio/vfio.c | 47 +++
On Wed, Feb 13, 2013 at 02:21:50PM +0100, Kevin Wolf wrote:
> iozone results with and without this series show significant difference
> for allocating writes:
>
> random random
>KB reclen write rewritereadrereadre
Am 14.02.2013 11:43, schrieb Stefan Hajnoczi:
> On Wed, Feb 13, 2013 at 02:21:50PM +0100, Kevin Wolf wrote:
>> iozone results with and without this series show significant difference
>> for allocating writes:
>>
>> random random
>>
- New VFIO_SET_IRQ ioctl option to pass the eventfd that is signaled
when
an error occurs in the vfio_pci_device
- Register pci_error_handler for the vfio_pci driver
- When the device encounters an error, the error handler registered by
the vfio_pci dr
- Create eventfd per vfio device assigned to a guest and register an
event handler
- This fd is passed to the vfio_pci driver through the SET_IRQ ioctl
- When the device encounters an error, the eventfd is signalled
and the qemu eventfd handler gets inv
On 14 December 2012 22:53, Antoine Mathys wrote:
> The proper mapping between 24 hours and 12 hours modes is:
> 0 12 AM
> 1-111-11 AM
> 12 12 PM
> 13-23 1-11 PM
> Fix code accordingly.
>
> Signed-off-by: Antoine Mathys
Sorry, I missed this patch earlier.
Reviewed-by: Peter Mayde
On 8 February 2013 12:32, Peter Maydell wrote:
> Hi; I spent yesterday working out how to run the Linux Test
> Project's syscall test suite under QEMU's linux-user mode,
> and I wrote up the instructions here for other peoples'
> benefit:
> http://wiki.qemu.org/Testing/LTP
> Currently ARM manage
Am 14.02.2013 02:23, schrieb Anthony Green:
> This patch adds all of the target-moxie code to the new moxie port.
>
>
> Signed-off-by: Anthony Green
> ---
> target-moxie/Makefile.objs |2 +
> target-moxie/cpu-qom.h | 70 +++
> target-moxie/cpu.c | 84 +++
> target-moxie/cpu.
On Wed, Feb 13, 2013 at 05:17:44PM +0100, Igor Mammedov wrote:
> qemu boots from disk image 3 times faster than direct kernel load.
That's surprising. Do you have any idea why that happens?
(CCing qemu-devel in case other QEMU developers can explain it)
> Use grub2-mkrescue tool to create boot
On Wed, Feb 13, 2013 at 04:33:33PM +0100, Igor Mammedov wrote:
> From: Andreas Färber
>
> Depends on http://lists.gnu.org/archive/html/qemu-devel/2013-02/msg00677.html
>
> Move x86_def_t definition to header and embed into X86CPUClass.
> Register types per built-in model definition.
>
> Move ve
Am 14.02.2013 12:32, schrieb Peter Maydell:
> On 14 February 2013 11:29, Andreas Färber wrote:
>> Am 14.02.2013 12:11, schrieb Peter Maydell:
>>> On 14 December 2012 22:53, Antoine Mathys wrote:
The proper mapping between 24 hours and 12 hours modes is:
> [snip]
>
>>> (and I've had confirma
On 14 February 2013 11:44, Andreas Färber wrote:
> Am 14.02.2013 12:32, schrieb Peter Maydell:
>> On 14 February 2013 11:29, Andreas Färber wrote:
>>> I may be repeating myself here, but adding qtests as requested would've
>>> caught this.
>>
>> Er, only if the tests were testing for the right th
On 14 February 2013 11:29, Andreas Färber wrote:
> Am 14.02.2013 12:11, schrieb Peter Maydell:
>> On 14 December 2012 22:53, Antoine Mathys wrote:
>>> The proper mapping between 24 hours and 12 hours modes is:
[snip]
>> (and I've had confirmation from somebody that this change
>> makes us match
Hi,
On 02/12/2013 11:01 PM, Hans de Goede wrote:
Hi,
On 02/12/2013 05:46 PM, Gerd Hoffmann wrote:
On 02/12/13 15:38, Jan Kiszka wrote:
Hi,
was just debugging a memory corruption of my USB driver inside QEMU -
and so far only there:
I have a queue registered with the UHCI controller on an in
As of commit 5928023c these pflash_cfi01 messages are now suppressed, so
this bug will be fixed in the next release of QEMU (1.4.0) and qemu-
linaro (2012.03).
** Changed in: qemu-linaro
Status: New => Fix Committed
** Changed in: qemu
Status: New => Fix Committed
** Changed in: q
On Thu, Feb 14, 2013 at 11:25:05AM +0100, Andreas Färber wrote:
> Am 14.02.2013 08:55, schrieb Gleb Natapov:
> > On Wed, Feb 13, 2013 at 12:43:10PM +0100, Jan Kiszka wrote:
> >> Python may otherwise decide to to read larger chunks, applying the seek
> >> only on the software buffer. This will retur
On Thu, 14 Feb 2013 10:45:22 +0100
Markus Armbruster wrote:
> [Note cc: +Laszlo, +Anthony, -qemu-trivial]
>
> Luiz Capitulino writes:
>
> > On Fri, 08 Feb 2013 20:34:20 +0100
> > Markus Armbruster wrote:
> >
> >> > The real problem here is that the k, M, G suffixes, for example, are not
> >>
Am 13.02.2013 23:27, schrieb Anthony Green:
> Add a simple moxie target, similar to what we have in the gdb simulator today.
>
>
> Signed-off-by: Anthony Green
> ---
> hw/moxie/Makefile.objs | 5 ++
> hw/moxiesim.c | 200
> +
> inc
Am 14.02.2013 12:11, schrieb Peter Maydell:
> On 14 December 2012 22:53, Antoine Mathys wrote:
>> The proper mapping between 24 hours and 12 hours modes is:
>> 0 12 AM
>> 1-111-11 AM
>> 12 12 PM
>> 13-23 1-11 PM
>> Fix code accordingly.
>>
>> Signed-off-by: Antoine Mathys
>
> So
Il 14/02/2013 12:18, Eduardo Habkost ha scritto:
>> > qemu boots from disk image 3 times faster than direct kernel load.
> That's surprising. Do you have any idea why that happens?
Because kernel load uses MMIO (from fw_cfg), while booting from disk
uses at worst PCI DMA and at best virtio.
Paolo
Just a note that IME trying to debug QEMU under gdb on MacOS doesn't
work very well. In particular as far as I can tell gdb breaks sigwait()
such that the sigwait() in sigwait_compat() can return 0 without setting
the int* sig. This causes QEMU to write an uninitialized value into the
qemu_signalfd
Il 14/02/2013 12:44, Andreas Färber ha scritto:
> What seems more likely is that we would
> have written a qtest which checked for the same wrong
> behaviour we incorrectly put into the code, which
> doesn't help anybody.
Hmm, that's not how I write tests... You write them as black boxes, and
if
Il 14/02/2013 12:29, Andreas Färber ha scritto:
> I may be repeating myself here, but adding qtests as requested would've
> caught this. And they should even more be added to avoid regressions.
> There's even templates to copy for RTC, and the new Big Endian-safe
> {read,write}[bwlq]() functions fo
It looks like this is only a problem in Thumb mode; the equivalent bug
in ARM mode was fixed in commit c67b6b71 back in 2009.
Can you make the test case dtb and image available? That would help in
testing...
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notificat
Hi,
>> The only fix I can think of is allocating a receive buffer inside
>> the UHCI code for read transfers, and copy the result over to the
>> guest memory when we are re-scanning the schedule, encounter the
>> completed td and are going to signal its completion to the guest.
> I could take a
I believe this bug was fixed on master by commit c128d6a6 in November,
and that fix made it into QEMU 1.3.0, so I'm closing this bug as fix
released.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Am 14.02.2013 13:17, schrieb Paolo Bonzini:
> Il 14/02/2013 12:44, Andreas Färber ha scritto:
>> What seems more likely is that we would
>> have written a qtest which checked for the same wrong
>> behaviour we incorrectly put into the code, which
>> doesn't help anybody.
>
> Hmm, that's not how I
On Thu, 14 Feb 2013 15:10:36 +0900
Tomoki Sekiyama wrote:
> Rename 'class' member in class_info of PciDeviceInfo to 'dev_class', and
> add some casts to avoid errors from c++ compiler.
[...]
> #
> # @class_info.desc: #optional a string description of the device's class
> #
> -# @class_info.c
On 14 February 2013 12:17, Paolo Bonzini wrote:
> Il 14/02/2013 12:44, Andreas Färber ha scritto:
>> What seems more likely is that we would
>> have written a qtest which checked for the same wrong
>> behaviour we incorrectly put into the code, which
>> doesn't help anybody.
>
> Hmm, that's not ho
Fix went out in QEMU 1.3.0.
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1028260
Title:
ARM: stellaris lm3s6965evb machine model
Closing as fixed, since the original build failure problems were fixed
some time ago, and the most recent quoted error message (garbage in a
system header file) strongly indicates either corrupt filesystem or
hardware issues with the build machine.
** Changed in: qemu
Status: Incomplete =>
I'm closing this bug as invalid since it has sat with insufficient
information to reproduce for more than six months with no further info
or followup from the original bug submitter. If you'd like to provide
the info I asked for, please feel free to reopen the bug and do so.
** Changed in: qemu
Closing as invalid since this is a build failure for an old version of
QEMU, appears to be a compiler/toolchain issue, and has had no followup
from the reporter in over a year.
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qe
QEMU now builds fine on MacOS, with LLVM-gcc and clang (we fixed both
the typedef problems and the global-fixed-register variable).
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEM
On Sun, Feb 10, 2013 at 10:10 PM, David Gibson
wrote:
>
> On Thu, Feb 07, 2013 at 09:28:20AM -0200, Erlon Cruz wrote:
> > From: Erlon Cruz
> >
> > This h_call is useful for DLPAR in future amongst other things. Given an
> > index
> > it fetches the corresponding PTE stored in the htab.
>
> Nice.
> It only segfaults when built with LLVM.
This was because of QEMU's use of a global-fixed-register variable. This
usage has now been removed and QEMU builds and runs fine with LLVM as
well as pure gcc.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notificatio
Closing as invalid for QEMU because it's an Incomplete bug against an
ancient QEMU version.
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/571
overlap flag in the region is currently unused, most devices have no
idea whether their region overlaps with anything, so drop it,
assume that all regions can overlap and always require priority.
It's also not clear how should devices allocate priorities.
As a first step, define a set of symbolic
On 14 February 2013 12:45, Michael S. Tsirkin wrote:
> overlap flag in the region is currently unused, most devices have no
> idea whether their region overlaps with anything, so drop it,
> assume that all regions can overlap and always require priority.
Devices themselves shouldn't care, for the
On Thu, Feb 14, 2013 at 12:56:02PM +, Peter Maydell wrote:
> On 14 February 2013 12:45, Michael S. Tsirkin wrote:
> > overlap flag in the region is currently unused, most devices have no
> > idea whether their region overlaps with anything, so drop it,
> > assume that all regions can overlap a
On Thu, 14 Feb 2013 09:18:53 -0200
Eduardo Habkost wrote:
> On Wed, Feb 13, 2013 at 05:17:44PM +0100, Igor Mammedov wrote:
> > qemu boots from disk image 3 times faster than direct kernel load.
>
> That's surprising. Do you have any idea why that happens?
>
> (CCing qemu-devel in case other QEM
On Thu, Feb 14, 2013 at 01:13:18PM +0100, Paolo Bonzini wrote:
> Il 14/02/2013 12:18, Eduardo Habkost ha scritto:
> >> > qemu boots from disk image 3 times faster than direct kernel load.
> > That's surprising. Do you have any idea why that happens?
>
> Because kernel load uses MMIO (from fw_cfg),
On 14 February 2013 13:09, Michael S. Tsirkin wrote:
> On Thu, Feb 14, 2013 at 12:56:02PM +, Peter Maydell wrote:
>> Up to the parent which controls the region being mapped into.
>
> We could just assume same priority as parent
Er, no. I mean the code in control of the parent MR sets the
prio
Il 14/02/2013 07:10, Tomoki Sekiyama ha scritto:
> diff --git a/qga/vss-win32-provider/Makefile b/qga/vss-win32-provider/Makefile
> new file mode 100644
> index 000..1f213f2
> --- /dev/null
> +++ b/qga/vss-win32-provider/Makefile
> @@ -0,0 +1,30 @@
> +-include ../../config-host.mak
> +-include
Il 14/02/2013 14:24, Eduardo Habkost ha scritto:
> On Thu, Feb 14, 2013 at 01:13:18PM +0100, Paolo Bonzini wrote:
>> Il 14/02/2013 12:18, Eduardo Habkost ha scritto:
> qemu boots from disk image 3 times faster than direct kernel load.
>>> That's surprising. Do you have any idea why that happens
[Some quoted material restored]
Luiz Capitulino writes:
> On Thu, 14 Feb 2013 10:45:22 +0100
> Markus Armbruster wrote:
>
>> [Note cc: +Laszlo, +Anthony, -qemu-trivial]
>>
>> Luiz Capitulino writes:
>>
>> > On Fri, 08 Feb 2013 20:34:20 +0100
>> > Markus Armbruster wrote:
>> >
>> >> > The re
Il 14/02/2013 07:10, Tomoki Sekiyama ha scritto:
> diff --git a/qga/vss-win32-provider/qga-provider.idl
> b/qga/vss-win32-provider/qga-provider.idl
> new file mode 100644
> index 000..17abca0
> --- /dev/null
> +++ b/qga/vss-win32-provider/qga-provider.idl
> @@ -0,0 +1,20 @@
> +import "oaidl.id
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/569760
Title:
Error in i386 cmpxchg instruction emulation
Status in QEMU:
Fix Relea
On Thu, Feb 14, 2013 at 11:56:34AM +0100, Kevin Wolf wrote:
> Am 14.02.2013 11:43, schrieb Stefan Hajnoczi:
> > On Wed, Feb 13, 2013 at 02:21:50PM +0100, Kevin Wolf wrote:
> >> iozone results with and without this series show significant difference
> >> for allocating writes:
> >>
> >>
On 02/13/2013 03:21 PM, Anthony Green wrote:
> This patch adds the disassembler logic for moxie.
When sending a patch series, it is better if you thread each message as
a reply to a cover letter, rather than each message as a top-level
thread ('git send-email -5 --cover-letter' is one way to easil
(ancient distro packaging bug so never valid for QEMU upstream itself;
marking Invalid there)
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/3
Richard Henderson writes:
Yes, and "-cpu Haswell" will enable the BMI extensions.
I have used git://repo.or.cz/qemu/rth.git x86-next checked out around 15
January for a while now. The host system is Debian GNU/Linux amd64 and
the guest is FreeBSD 9.1 amd64.
I now updated x86-next in order
(CCing virt-tools list in case they have any existing solutions or ideas
on how to make this easier for everybody)
On Thu, Feb 14, 2013 at 02:20:45PM +0100, Igor Mammedov wrote:
> On Thu, 14 Feb 2013 09:18:53 -0200
> Eduardo Habkost wrote:
>
> > On Wed, Feb 13, 2013 at 05:17:44PM +0100, Igor M
Hi,
On 02/14/2013 01:23 PM, Gerd Hoffmann wrote:
Hi,
The only fix I can think of is allocating a receive buffer inside
the UHCI code for read transfers, and copy the result over to the
guest memory when we are re-scanning the schedule, encounter the
completed td and are going to signal its
On Thu, Feb 14, 2013 at 01:22:18PM +, Peter Maydell wrote:
> On 14 February 2013 13:09, Michael S. Tsirkin wrote:
> > On Thu, Feb 14, 2013 at 12:56:02PM +, Peter Maydell wrote:
> >> Up to the parent which controls the region being mapped into.
> >
> > We could just assume same priority as
On Thu, Feb 14, 2013 at 3:09 PM, Michael S. Tsirkin wrote:
> On Thu, Feb 14, 2013 at 12:56:02PM +, Peter Maydell wrote:
>> On 14 February 2013 12:45, Michael S. Tsirkin wrote:
>> > overlap flag in the region is currently unused, most devices have no
>> > idea whether their region overlaps wit
On Thu, Feb 14, 2013 at 4:02 PM, Michael S. Tsirkin wrote:
> On Thu, Feb 14, 2013 at 01:22:18PM +, Peter Maydell wrote:
>> On 14 February 2013 13:09, Michael S. Tsirkin wrote:
>> > On Thu, Feb 14, 2013 at 12:56:02PM +, Peter Maydell wrote:
>> >> Up to the parent which controls the region
On 02/14/2013 11:41 AM, Eduardo Habkost wrote:
I'd glad to amend patch, if there are suggestions how to generalize it and
improve "create boot image" process for distros that doesn't have
grub2-mkrescue.
A reusable tool/script would be useful even outside virt-test. Anybody
who uses -kernel/-in
On Wed, Feb 13, 2013 at 02:21:51PM +0100, Kevin Wolf wrote:
> @@ -882,20 +876,55 @@ int qcow2_alloc_cluster_offset(BlockDriverState *bs,
> uint64_t offset,
> trace_qcow2_alloc_clusters_offset(qemu_coroutine_self(), offset,
>n_start, n_end);
>
> -/
On 14 February 2013 14:02, Michael S. Tsirkin wrote:
> Well that's the status quo. One of the issues is, you have
> no idea what else uses each priority. With this change,
> at least you can grep for it.
No, because most of the code you find will be setting
priorities for completely irrelevant co
Il 14/02/2013 07:10, Tomoki Sekiyama ha scritto:
> To enable VSS support in qemu-ga for Windows, header files included in
> VSS SDK is required.
> The VSS support is enabled when the option like below:
> ./configure --with-vss-sdk="/pass/to/VSS SDK"
>
> VSS SDK is available from:
> http://www.
On Thu, Feb 14, 2013 at 04:14:39PM +0200, Avi Kivity wrote:
> On Thu, Feb 14, 2013 at 3:09 PM, Michael S. Tsirkin wrote:
> > On Thu, Feb 14, 2013 at 12:56:02PM +, Peter Maydell wrote:
> >> On 14 February 2013 12:45, Michael S. Tsirkin wrote:
> >> > overlap flag in the region is currently unus
On Thu, Feb 14, 2013 at 02:31:38PM +0100, Paolo Bonzini wrote:
> Il 14/02/2013 14:24, Eduardo Habkost ha scritto:
> > On Thu, Feb 14, 2013 at 01:13:18PM +0100, Paolo Bonzini wrote:
> >> Il 14/02/2013 12:18, Eduardo Habkost ha scritto:
> > qemu boots from disk image 3 times faster than direct ke
On Thu, Feb 14, 2013 at 02:34:20PM +, Peter Maydell wrote:
> On 14 February 2013 14:02, Michael S. Tsirkin wrote:
> > Well that's the status quo. One of the issues is, you have
> > no idea what else uses each priority. With this change,
> > at least you can grep for it.
>
> No, because most o
On Wed, Feb 13, 2013 at 02:21:53PM +0100, Kevin Wolf wrote:
> Signed-off-by: Kevin Wolf
> ---
> block/qcow2-cluster.c | 40
> block/qcow2.h | 11 +++
> 2 files changed, 39 insertions(+), 12 deletions(-)
>
> diff --git a/block/qcow2-clu
Il 13/02/2013 23:21, Anthony Green ha scritto:
> +/* Disassemble moxie instructions.
> + Copyright 2009
> + Free Software Foundation, Inc.
> +
> + This file is part of the GNU opcodes library.
> +
> + This library is free software; you can redistribute it and/or modify
> + it under the te
On Thu, Feb 14, 2013 at 4:40 PM, Michael S. Tsirkin wrote:
> On Thu, Feb 14, 2013 at 04:14:39PM +0200, Avi Kivity wrote:
>
> But some parents are system created and shared by many devices so children for
> such have no idea who their siblings are.
>
> Please take a look at the typical map in this
Il 14/02/2013 02:47, Richard Henderson ha scritto:
> Both uses of ctz have already eliminated zero, and thus the difference
> in edge conditions between the two routines is irrelevant.
>
> Signed-off-by: Richard Henderson
> ---
> include/qemu/hbitmap.h | 3 ++-
> util/hbitmap.c | 3 ++-
>
On Thu, 14 Feb 2013 09:44:59 -0200
Eduardo Habkost wrote:
> On Wed, Feb 13, 2013 at 04:33:33PM +0100, Igor Mammedov wrote:
> > From: Andreas Färber
> >
> > Depends on
> > http://lists.gnu.org/archive/html/qemu-devel/2013-02/msg00677.html
> >
> > Move x86_def_t definition to header and embed in
On Thu, Feb 14, 2013 at 11:39 AM, harryxiyou wrote:
> On Tue, Feb 12, 2013 at 5:21 AM, Stefan Hajnoczi wrote:
>> On Thu, Feb 7, 2013 at 4:19 PM, Stefan Hajnoczi wrote:
>>> I believe Google will announce GSoC again this year (there is
>>> no guarantee though) and I have created the wiki page so w
CC'ing some more people from the "debug output revamp" RFC discussion.
Am 11.02.2013 20:01, schrieb Andreas Färber:
> From: Andreas Färber
>
> Signed-off-by: Andreas Färber
> ---
> hw/tmp105.c | 27 +--
> 1 Datei geändert, 25 Zeilen hinzugefügt(+), 2 Zeilen entfernt(-
Blue,
Am 27.01.2013 14:32, schrieb Andreas Färber:
> Signed-off-by: Andreas Färber
> ---
> target-sparc/ldst_helper.c |2 +-
> 1 Datei geändert, 1 Zeile hinzugefügt(+), 1 Zeile entfernt(-)
>
> diff --git a/target-sparc/ldst_helper.c b/target-sparc/ldst_helper.c
> index cf1bddf..7decd66 1006
On Thu, Feb 14, 2013 at 04:13:22PM +0100, Igor Mammedov wrote:
> On Thu, 14 Feb 2013 09:44:59 -0200
> Eduardo Habkost wrote:
[...]
> > > +if (kvm_enabled()) {
> > > +typename = g_strdup_printf("%s-kvm-" TYPE_X86_CPU, name);
> >
> > * Could we use the "-tcg" suffix for the non-KVM mode
Hi All
I use the following code to insert a breakpoint in physical address
0×160CPUArchState *cpu = first_cpu;
hwaddr addr;
sscanf(command + 2, "%ld", &addr);
int err = cpu_breakpoint_insert(cpu, addr, BP_GDB, NULL );qemu successfully hit
the breakpoint and stop, then i try to single-step
On 02/13/2013 06:47 PM, Richard Henderson wrote:
> Version 1 merely tried to adjust bitops_flsl, here I instead eliminate
> it all from bitops.h, and standardizes on the routines from host-utils.h.
>
>
> r~
>
>
> Richard Henderson (10):
> host-utils: Add host long specific aliases for clz, ct
On Thu, 14 Feb 2013 14:31:50 +0100
Markus Armbruster wrote:
> [Some quoted material restored]
>
> Luiz Capitulino writes:
>
> > On Thu, 14 Feb 2013 10:45:22 +0100
> > Markus Armbruster wrote:
> >
> >> [Note cc: +Laszlo, +Anthony, -qemu-trivial]
> >>
> >> Luiz Capitulino writes:
> >>
> >> >
On Thu, Feb 14, 2013 at 03:48:51PM +0100, Stefan Hajnoczi wrote:
> On Wed, Feb 13, 2013 at 02:21:53PM +0100, Kevin Wolf wrote:
> > Signed-off-by: Kevin Wolf
> > ---
> > block/qcow2-cluster.c | 40
> > block/qcow2.h | 11 +++
> > 2 files
Hi; I'm looking for test images (and command lines) for the musicpal
and milkymist targets, because I have a patchset which makes some
changes to them [I'm trying to get rid of sysbus_add_memory()].
Does anybody have any to hand?
thanks
-- PMM
On Thu, Feb 14, 2013 at 05:07:02PM +0200, Avi Kivity wrote:
> On Thu, Feb 14, 2013 at 4:40 PM, Michael S. Tsirkin wrote:
> > On Thu, Feb 14, 2013 at 04:14:39PM +0200, Avi Kivity wrote:
> >
> > But some parents are system created and shared by many devices so children
> > for
> > such have no idea
1 - 100 of 192 matches
Mail list logo
