On 09/08/2010 06:07 PM, Stefan Hajnoczi wrote:
uint32_t table_size; /* table size, in clusters */
Presumably L1 table size? Or any table size?
Hm. It would be nicer not to require contiguous sectors anywhere. How
about a variable- or fixed-height tree?
Both extents and fancie
Any additional questions about this patch series?
Prerna and I are keen on growing trace event coverage and putting
static tracing to use outside our own development environments. It
has been a powerful tool for block layer performance work and
developing QED, and I think it will be useful to oth
> commit 8b33d9eeba91422ee2d73b6936ad57262d18cf5a
> Author: Anthony Liguori
> Date: Wed Sep 8 17:09:15 2010 -0500
>
> Revert "Make default invocation of block drivers safer (v3)"
>
> This reverts commit 79368c81bf8cf93864d7afc88b81b05d8f0a2c90.
>
> Conflicts:
>
>
On 09/07/2010 07:08 AM, Kevin Wolf wrote:
Recenty a patch was committed to protect the first four bytes of an image to
avoid "converting" a probed raw image to a different format when a malicious
guest writes e.g. a qcow2 header to it.
This check relies on the assumption that all qiov entries ar
On 09/09/2010 06:35 AM, Kevin Wolf wrote:
commit 8b33d9eeba91422ee2d73b6936ad57262d18cf5a
Author: Anthony Liguori
Date: Wed Sep 8 17:09:15 2010 -0500
Revert "Make default invocation of block drivers safer (v3)"
This reverts commit 79368c81bf8cf93864d7afc88b81b05d8f0a2c90.
Conf
Am 09.09.2010 14:30, schrieb Anthony Liguori:
> On 09/07/2010 07:08 AM, Kevin Wolf wrote:
>> Recenty a patch was committed to protect the first four bytes of an image to
>> avoid "converting" a probed raw image to a different format when a malicious
>> guest writes e.g. a qcow2 header to it.
>>
>>
On 09/09/2010 01:45 AM, Avi Kivity wrote:
Loading very large L2 tables on demand will result in very long
latencies. Increasing cluster size will result in very long first
write latencies. Adding an extra level results in an extra random
write every 4TB.
It would be trivially easy to add an
On 09/09/2010 07:44 AM, Kevin Wolf wrote:
Isn't this an unbounded, guest controlled, malloc? IOW, a guest could
do a request of 4GB and on a 32-bit system crash the qemu instance.
If you're concerned about that, we need to ban qemu_iovec_to_buffer()
completely. Currently we do the same th
Am 09.09.2010 14:52, schrieb Anthony Liguori:
> On 09/09/2010 07:44 AM, Kevin Wolf wrote:
>>> Isn't this an unbounded, guest controlled, malloc? IOW, a guest could
>>> do a request of 4GB and on a 32-bit system crash the qemu instance.
>>>
>> If you're concerned about that, we need to ban qe
On 09/09/2010 08:02 AM, Kevin Wolf wrote:
Or instead of completely removing it, we could add
a size limit, though I suspect that would mean violating some specs.
One thing I was thinking of trying was splitting off the first sector
into a linear buffer, then allocating a new iovec an
2010/9/8 Hervé Poussineau :
> Use it in Jazz emulation
> Remove protection stuff, which doesn't belong to this device
> Remove ds1225y_init() and ds1225y_set_protection() functions, which are not
> used anymore
>
> Signed-off-by: Hervé Poussineau
> ---
> hw/ds1225y.c | 151
>
2010/9/8 Hervé Poussineau :
> Use it in Jazz emulation
> Remove isa_vga_mm_init() function, which is not used anymore
>
> Signed-off-by: Hervé Poussineau
> ---
> hw/mips_jazz.c | 2 +-
> hw/pc.h | 2 -
> hw/vga-isa-mm.c | 94
>
2010/9/8 Hervé Poussineau :
> Use it in Jazz emulation
> Remove g364fb_mm_init() function, which is not used anymore
>
> Signed-off-by: Hervé Poussineau
> ---
> hw/g364fb.c | 120 +--
> hw/mips.h | 5 --
> hw/mips_jazz.c | 2 +-
>
2010/9/8 Hervé Poussineau :
> Use it in Jazz emulation
> Remove rc4030_init() function, which is not used anymore
>
> Signed-off-by: Hervé Poussineau
> ---
> hw/mips.h | 4 +-
> hw/mips_jazz.c | 8 +--
> hw/rc4030.c | 135 ++-
> 3
On 09/09/2010 02:49 PM, Anthony Liguori wrote:
We should optimize for the future. That means a btrfs file system and/or
enterprise storage.
So we should just implement a copy-on-read wrapper that generates a
sparse raw image and uses FIEMAP (or whatever it is called these days)
to test for th
On 09/09/2010 11:48 AM, Paolo Bonzini wrote:
On 09/09/2010 02:49 PM, Anthony Liguori wrote:
We should optimize for the future. That means a btrfs file system and/or
enterprise storage.
So we should just implement a copy-on-read wrapper that generates a
sparse raw image and uses FIEMAP (or wha
Am 16.07.2010 09:04, schrieb Markus Armbruster:
Stefan Weil writes:
An empty environment is sometimes useful in user mode.
The new option provides it for linux-user and bsd-user
(darwin-user still has no environment related options).
Stupid question: why is /usr/bin/env insufficient
Am 03.08.2010 11:48, schrieb Juan Quintela:
Stefan Weil wrote:
Fix some inconsistencies (tabs and punctuation)
and try to improve grammar and spelling.
Cc: Juan Quintela
Signed-off-by: Stefan Weil
Acked-by: Juan Quintela
Anthony, please apply.
Stefan, thanks very much for the impr
On 09/09/2010 12:30 PM, Stefan Weil wrote:
Am 16.07.2010 09:04, schrieb Markus Armbruster:
Stefan Weil writes:
An empty environment is sometimes useful in user mode.
The new option provides it for linux-user and bsd-user
(darwin-user still has no environment related options).
Stupid question
Am 08.08.2010 14:09, schrieb Stefan Weil:
Character devices created by qemu_chr_open don't
allow duplicate device names, so naming all
UART devices "null" no longer works.
Running "qemu-system-arm -M n800" (and some other machines)
results in this error message:
qemu-system-arm: Duplica
Am 11.08.2010 18:21, schrieb Blue Swirl:
On Mon, Aug 9, 2010 at 2:43 PM, Stefan Weil wrote:
Symbols with a size of 0 are unusable for the disassembler.
Example:
While running an arm linux kernel, no symbolic names are
used in qemu.log when the cpu is executing an assembler function.
On 09/09/2010 01:59 AM, Avi Kivity wrote:
On 09/08/2010 06:07 PM, Stefan Hajnoczi wrote:
uint32_t table_size; /* table size, in clusters */
Presumably L1 table size? Or any table size?
Hm. It would be nicer not to require contiguous sectors anywhere. How
about a variable- or
Am 09.08.2010 16:48, schrieb Stefan Weil:
ELF images were not detected as linux kernels.
Assume that they are linux kernels if the kernel name contains 'vmlinux'.
Cc: Paul Brook
Signed-off-by: Stefan Weil
---
hw/arm_boot.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff
On Thu, Sep 9, 2010 at 3:48 AM, john cooper wrote:
> Blue Swirl wrote:
>> On Tue, Sep 7, 2010 at 12:31 PM, john cooper wrote:
>>> Failure by qemu to open a default config file isn't cause to
>>> error exit -- it just quietly continues on. After puzzling
>>> issues with otherwise opaque config f
On Thu, Sep 9, 2010 at 5:42 PM, Stefan Weil wrote:
> Am 11.08.2010 18:21, schrieb Blue Swirl:
>>
>> On Mon, Aug 9, 2010 at 2:43 PM, Stefan Weil wrote:
>>
>>>
>>> Symbols with a size of 0 are unusable for the disassembler.
>>>
>>> Example:
>>>
>>> While running an arm linux kernel, no symbolic nam
Am 09.09.2010 20:44, schrieb Blue Swirl:
On Thu, Sep 9, 2010 at 5:42 PM, Stefan Weil wrote:
Am 11.08.2010 18:21, schrieb Blue Swirl:
On Mon, Aug 9, 2010 at 2:43 PM, Stefan Weil
wrote:
Symbols with a size of 0 are unusable for the disassembler.
Example:
While running an arm linux kerne
On Thu, Sep 9, 2010 at 7:11 PM, Stefan Weil wrote:
> Am 09.09.2010 20:44, schrieb Blue Swirl:
>>
>> On Thu, Sep 9, 2010 at 5:42 PM, Stefan Weil wrote:
>>>
>>> Am 11.08.2010 18:21, schrieb Blue Swirl:
On Mon, Aug 9, 2010 at 2:43 PM, Stefan Weil
wrote:
>
> Symbols with
According to Antony, Riku is the maintainer for Linux user,
so make this visible for everyone.
(The patch also fixes a whitespace issue at end of line -
required by git and by my editor).
Cc: Riku Voipio
Cc: Antony Liguori
Signed-off-by: Stefan Weil
---
MAINTAINERS |4 ++--
1 files change
Am 09.09.2010 21:29, schrieb Blue Swirl:
On Thu, Sep 9, 2010 at 7:11 PM, Stefan Weil wrote:
Am 09.09.2010 20:44, schrieb Blue Swirl:
On Thu, Sep 9, 2010 at 5:42 PM, Stefan Weil wrote:
Am 11.08.2010 18:21, schrieb Blue Swirl:
On Mon, Aug 9, 2010 at 2:43 PM, Stefan
On Thu, Sep 9, 2010 at 7:34 PM, Stefan Weil wrote:
> Am 09.09.2010 21:29, schrieb Blue Swirl:
>>
>> On Thu, Sep 9, 2010 at 7:11 PM, Stefan Weil wrote:
>>
>>>
>>> Am 09.09.2010 20:44, schrieb Blue Swirl:
>>>
On Thu, Sep 9, 2010 at 5:42 PM, Stefan Weil
wrote:
>
> Am 11.
Am 09.09.2010 um 21:32 schrieb Stefan Weil:
According to Antony, Riku is the maintainer for Linux user,
so make this visible for everyone.
You beat me! :)
Acked-by: Andreas Färber
Andreas
(The patch also fixes a whitespace issue at end of line -
required by git and by my editor).
Cc: Rik
Am 09.09.2010 21:43, schrieb Andreas Färber:
Am 09.09.2010 um 21:32 schrieb Stefan Weil:
According to Antony, Riku is the maintainer for Linux user,
so make this visible for everyone.
You beat me! :)
Acked-by: Andreas Färber
Andreas
(The patch also fixes a whitespace issue at end of line
According to Anthony, Riku is the maintainer for Linux user,
so make this visible for everyone.
(The patch also fixes a whitespace issue at end of line -
required by git and by my editor).
Cc: Riku Voipio
Cc: Anthony Liguori
Signed-off-by: Stefan Weil
---
MAINTAINERS |4 ++--
1 files chan
The goal of this file is not to establish strict ownership of the code base but
rather to provide a place for people to direct questions to and for names of
people to CC on patches.
I'm basing this update on my observations on how things currently work today.
If you think your name should be on so
On 09/09/2010 02:50 PM, Stefan Weil wrote:
According to Anthony, Riku is the maintainer for Linux user,
so make this visible for everyone.
(The patch also fixes a whitespace issue at end of line -
required by git and by my editor).
Cc: Riku Voipio
Cc: Anthony Liguori
Signed-off-by: Stefan Weil
Am 09.09.2010 21:54, schrieb Anthony Liguori:
The goal of this file is not to establish strict ownership of the code base but
rather to provide a place for people to direct questions to and for names of
people to CC on patches.
This text should be added to MAINTAINERS.
I'm basing this upd
On Thu, Sep 9, 2010 at 7:54 PM, Anthony Liguori wrote:
> The goal of this file is not to establish strict ownership of the code base
> but
> rather to provide a place for people to direct questions to and for names of
> people to CC on patches.
>
> I'm basing this update on my observations on how
On 09/09/2010 03:12 PM, Stefan Weil wrote:
Am 09.09.2010 21:54, schrieb Anthony Liguori:
The goal of this file is not to establish strict ownership of the
code base but
rather to provide a place for people to direct questions to and for
names of
people to CC on patches.
This text should be a
Hi,
Is it possible, as of today, to emulate a classic Linux framebuffer when
using qemu linux-user mode?
At a first glance, I saw in the code that
FBIOGET_FSCREENINFO, FBIOGET_VSCREENINFO and FBIOPUT_VSCREENINFO being
declared by couldn't locate where they're handled. Are these hooked to the
SDL
On 09/09/2010 03:12 PM, Blue Swirl wrote:
diff --git a/MAINTAINERS b/MAINTAINERS
index e5165fb..ee84f3f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4,13 +4,12 @@ QEMU Maintainers
Project leaders:
-Fabrice Bellard
Paul Brook
+Anthony Liguori
I think that is how t
Am 08.09.2010 um 03:19 schrieb malc:
On Wed, 8 Sep 2010, Alexander Graf wrote:
On 08.09.2010, at 00:48, malc wrote:
On Wed, 8 Sep 2010, Andreas F?rber wrote:
What I don't intend to investigate any time soon is
the chatty CoreAudio code.
What about it?
It throws about 100 warnings when c
On Thu, Sep 9, 2010 at 8:19 PM, Ilyes Gouta wrote:
> Hi,
> Is it possible, as of today, to emulate a classic Linux framebuffer when
> using qemu linux-user mode?
> At a first glance, I saw in the code that
> FBIOGET_FSCREENINFO, FBIOGET_VSCREENINFO and FBIOPUT_VSCREENINFO being
> declared by could
On Tue, 7 Sep 2010 17:25:20 -0700
Chris Wright wrote:
> From: Cam Macdonell
>
> * Cam Macdonell (c...@cs.ualberta.ca) wrote:
> > It seems it was the alignment value being passed back from
> > pci_resource_alignment(). The return type is an int, which was
> > causing value of 2GB to be sign ext
On Thu, Sep 09, 2010 at 12:43:28PM -0500, Anthony Liguori wrote:
> Define "very large disks".
>
> My target for VM images is 100GB-1TB. Practically speaking, that at
> least covers us for the next 5 years.
We have 2TB SATA disks shipping already, and people tend to produce
more and more "data".
On Thu, Sep 09, 2010 at 12:02:26PM -0500, Anthony Liguori wrote:
> My position is that we'll need a sparse image format well into the
> future because while btrfs may be ubiquitous as a file system, IRL,
> people transfer images around all of the time through dumb transports
> like HTTP and fat-
On Thu, Sep 09, 2010 at 09:24:26AM +0300, Avi Kivity wrote:
> The other thing we can do is defragment the logical image, then
> defragment the underlying file (if the filesystem supports it, issue the
> appropriate ioctl, otherwise defragment to a new file which you write
> linearly).
What's wh
On Thu, Sep 09, 2010 at 07:36:28PM +, Blue Swirl wrote:
> On Thu, Sep 9, 2010 at 7:34 PM, Stefan Weil wrote:
> > Am 09.09.2010 21:29, schrieb Blue Swirl:
> >>
> >> On Thu, Sep 9, 2010 at 7:11 PM, Stefan Weil wrote:
> >>
> >>>
> >>> Am 09.09.2010 20:44, schrieb Blue Swirl:
> >>>
>
>
On Thu, Sep 9, 2010 at 9:39 PM, Ilyes Gouta wrote:
> Hi,
>
> Well, actually I'd like to run sh4 binaries in linux-user mode, where these
> are actually DirectFB applications which rely on the standard Linux
> framebuffer to display things.
>
> In my use case, I'd like to route these ioctl in qemu
On Thu, 9 Sep 2010, Andreas F?rber wrote:
> Am 08.09.2010 um 03:19 schrieb malc:
>
> > On Wed, 8 Sep 2010, Alexander Graf wrote:
> >
> > > On 08.09.2010, at 00:48, malc wrote:
> > >
> > > > On Wed, 8 Sep 2010, Andreas F?rber wrote:
> > > > > What I don't intend to investigate any time soon is
>
Hi,
> No, but it could be possible to convert the DirectFB ioctl structures
> between guest and host. Other ioctls are translated this way. I guess
> nobody has cared about framebuffer support yet.
DirectFB (on the sh4 side) is just a client which is interacting with the
framebuffer. It doesn't h
On 09.09.2010, at 23:06, Ilyes Gouta wrote:
>
>
> On Thu, Sep 9, 2010 at 9:39 PM, Ilyes Gouta wrote:
> Hi,
>
> Well, actually I'd like to run sh4 binaries in linux-user mode, where these
> are actually DirectFB applications which rely on the standard Linux
> framebuffer to display things.
>
On Thu, Sep 9, 2010 at 11:57 PM, Alexander Graf wrote:
>
> On 09.09.2010, at 23:06, Ilyes Gouta wrote:
>
> >
> >
> > On Thu, Sep 9, 2010 at 9:39 PM, Ilyes Gouta
> wrote:
> > Hi,
> >
> > Well, actually I'd like to run sh4 binaries in linux-user mode, where
> these are actually DirectFB applicatio
From: edison
In order to backup snapshots, created from QCOW2 iamge, we want to copy
snapshots out of QCOW2 disk to a seperate storage.
The following patch adds a new option in "qemu-img": qemu-img convert -f qcow2
-O qcow2 -s snapshot_name src_img bck_img.
Right now, it only supports to copy t
On 9/7/2010 9:41 AM, Venkateswararao Jujjuri (JV) wrote:
Bruno Cesar Ribas wrote:
On Thu, Aug 26, 2010 at 09:44:32AM -0700, Venkateswararao Jujjuri (JV) wrote:
Bruno Cesar Ribas wrote:
Hi,
[snip]
This quick test is with QEMU patches that are on mailing lists but not merged
into mainline.
Bei
Hi,
On 16 August 2010 22:26, Janne Huttunen wrote:
> Yes, your version works (both on paper and in practice). I'm not
> quite sure I like the way it breaches the apparent abstraction
> of the FIFO handling routines (if you can call it that) or the
> way it first gives FIFO slots back to the guest
From: edison
Add a new option when "savevm": savevm -n snapshotName, which only takes
snapshot on disk, but doesn't save vm state(memory,cpu,devices...).
Saving vm state on QCOW2 disk will take a long time, per my test, it will take
1~2 minutes to "savevm" on VM with 1G memory. Even worse, the
On 09/09/2010 08:43 PM, disheng...@gmail.com wrote:
From: edison
Add a new option when "savevm": savevm -n snapshotName, which only takes
snapshot on disk, but doesn't save vm state(memory,cpu,devices...).
Saving vm state on QCOW2 disk will take a long time, per my test, it will take 1~2 minute
http://www.seabios.org/pipermail/seabios/2010-July/000796.html
I haven't found my time to respin to check PMM stuff yet.
If you give it a try, it would be appreciated.
thanks,
On Thu, Sep 09, 2010 at 02:07:13PM -0500, Adnan Khaleel wrote:
> Can you point me to this patch? I found one for BAR ove
I make no claims that this is accurate or exhaustive but I think it's a
reasonable place to start.
As the file mentions, the purpose of this file is to give contributors
information about who they can go to with questions about a particular piece of
code or who they can ask for review.
If you sig
On Thu, Sep 09, 2010 at 04:18:37PM -0500, Anthony Liguori wrote:
> I make no claims that this is accurate or exhaustive but I think it's a
> reasonable place to start.
>
> As the file mentions, the purpose of this file is to give contributors
> information about who they can go to with questions a
On 09.09.2010, at 23:18, Anthony Liguori wrote:
> I make no claims that this is accurate or exhaustive but I think it's a
> reasonable place to start.
>
> As the file mentions, the purpose of this file is to give contributors
> information about who they can go to with questions about a particul
On 09/09/2010 04:35 PM, Edgar E. Iglesias wrote:
+CRIS Machines
+-
+etraxfs
+M: Edgar E. Iglesias
+S: Maintained
+F: hw/etraxfs.c
+
+Axis Dev88
+M: Edgar E. Iglesias
+S: Maintained
+F: hw/axis_dev88.c
+
+MicroBlaze
For consistency, this should be:
MicroBlaze Machines
-
62 matches
Mail list logo
