On 14.03.2011, at 22:21, François Revol wrote:
> The OSX build has been broken for some time now...
>
> * qemu-thread-posix.c:
> both qemu_mutex_timedlock and qemu_cond_timedwait make use of clock_gettime()
> and CLOCK_REALTIME, which OSX doesn't have.
> It seems like both functions are nowhere
** Tags removed: kvm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/712416
Title:
kvm_intel kernel module crash with via nano vmx
Status in QEMU:
New
Status in “kvm” package in Ubuntu:
Incomple
** Tags added: kvm
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/712416
Title:
kvm_intel kernel module crash with via nano vmx
Status in QEMU:
New
Status in “kvm” package in Ubuntu:
Incomplete
On Thu, Mar 10, 2011 at 11:03 PM, Michael Tokarev wrote:
> qemu now has generic bitmap functions,
> so don't redefine them in sheepdog.c,
> use common header instead. A small cleanup.
>
> Here's only one function which is actually
> used in sheepdog and gets replaced with
> a generic one (simplif
** Changed in: qemu-kvm (Ubuntu Maverick)
Status: New => In Progress
** Changed in: qemu-kvm (Ubuntu Lucid)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bug
** Attachment added: "amd64 debs for maverick"
https://bugs.launchpad.net/qemu/+bug/584143/+attachment/1909178/+files/hdd-mav-debs.tgz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/584143
Title:
** Attachment added: "amd64 debs for lucid"
https://bugs.launchpad.net/qemu/+bug/584143/+attachment/1909175/+files/hdd-lucid-debs.tgz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/584143
Title:
On Tue, Mar 08, 2011 at 06:21:07PM +0100, Jan Kiszka wrote:
> On 2011-03-08 18:15, Paolo Bonzini wrote:
> > On 03/08/2011 06:10 PM, Jan Kiszka wrote:
> >>> The qemu.git bit seen with my win32 patch series should also be a
> >>> regression from qemu-kvm.git to qemu.git, no?
> >>
> >> Can't follow.
LinkedIn
wangsheng wang requested to add you as a connection on LinkedIn:
--
Jiajun,
I'd like to add you to my professional network on LinkedIn.
- wangsheng
Accept invitation from wangsheng wang
http://www.linkedin.com/e/-kkb1ec-gla8yek0-1f/qT
** Branch linked: lp:~serge-hallyn/ubuntu/maverick/qemu-kvm/hdd-serial
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/584143
Title:
qemu fails to set hdd serial number
Status in QEMU:
Fix Release
** Branch linked: lp:~serge-hallyn/ubuntu/lucid/qemu-kvm/hdd-serial
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/584143
Title:
qemu fails to set hdd serial number
Status in QEMU:
Fix Released
S
In order to proceed with SRU, we need someone to confirm that the debs
in comment #21 or #22 work for them.
** Description changed:
+ ==
+ SRU Justification:
+ 1. impact: 'qemu save' is slow
+ 2. how addressed: a patch upstream fixes the case when a file does not
** Attachment added: "amd64 debs for maverick"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/524447/+attachment/1909040/+files/slowsave-mav-debs.tgz
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Invalid
** Also affects: libvirt (Ubuntu Lucid)
Importance: Undecided
** Attachment added: "amd64 .debs for lucid"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/524447/+attachment/1908989/+files/slowsave-lucid-debs.tgz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.n
On Mar 15, 2011, at 2:49 AM, Anthony Liguori wrote:
> On 03/14/2011 11:36 AM, Juan Quintela wrote:
>> Jes Sorensen wrote:
>>> On 03/14/11 13:14, Juan Quintela wrote:
Please send any agenda items you are interested in covering.
Thanks, Juan.
>>> I presume you mean for March 15? To
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/648128
Title:
VirtFS: Cannot mount 9p during boot
Status in QEMU:
Fix Committed
Bug
Patch with fix is at http://patchwork.ozlabs.org/patch/77142/mbox/. It
is in 0.14.0 so marked natty bug as fix released. I will propose merge
of the fix for maverick and lucid.
** Changed in: qemu-kvm (Ubuntu)
Assignee: (unassigned) => Serge Hallyn (serge-hallyn)
** Also affects: qemu-kvm
** Branch linked: lp:~serge-hallyn/ubuntu/maverick/qemu-kvm/slowsave
** Branch linked: lp:~serge-hallyn/ubuntu/lucid/qemu-kvm/slowsave
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/524447
Title:
v
On Mon, Mar 14, 2011 at 09:56:23PM +0200, Blue Swirl wrote:
> On Mon, Mar 14, 2011 at 3:46 PM, wrote:
> > From: Edgar E. Iglesias
> >
> > Signed-off-by: Edgar E. Iglesias
> > ---
> > Makefile.target | 2 +
> > hw/xilinx_axidma.c | 463 +++
> > hw/xilinx_axidma.
> > > FVD's novel uses of the reference count table reduces the metadata
update
> > > overhead down to literally zero during normal execution of a VM.
This gets
> > > the bests of QCOW2's reference count table but without its
oeverhead. In
> > > FVD, the reference count table is only updated whe
The OSX build has been broken for some time now...
* qemu-thread-posix.c:
both qemu_mutex_timedlock and qemu_cond_timedwait make use of clock_gettime()
and CLOCK_REALTIME, which OSX doesn't have.
It seems like both functions are nowhere found. Can they be removed then ?
* cpus.c:
qemu_kvm_eat_si
From: Jordan Justen
When -pflash is specified, it will be mapped just below the
system rom (wjust below 4GB).
If -pflash is specified on the command line, but -bios is
not specified, then 'bios.bin' will NOT be loaded, and
instead the -pflash flash image will be mapped just below
4GB in place of
From: Jordan Justen
When checking pfl->rom_mode for when to lazily reenter ROMD mode,
the value was check was the opposite of what it should have been.
This prevent the part from returning to ROMD mode after a write
was made to the CFI rom region.
---
hw/pflash_cfi02.c |2 +-
1 files changed
On 03/14/2011 03:48 PM, Luiz Capitulino wrote:
On Mon, 14 Mar 2011 15:41:49 -0500
Anthony Liguori wrote:
On 03/14/2011 03:22 PM, Luiz Capitulino wrote:
On Mon, 14 Mar 2011 14:45:13 -0500
Anthony Liguori wrote:
On 03/14/2011 02:37 PM, Luiz Capitulino wrote:
qerror_abort() only exists for
On Mon, 14 Mar 2011 15:41:49 -0500
Anthony Liguori wrote:
> On 03/14/2011 03:22 PM, Luiz Capitulino wrote:
> > On Mon, 14 Mar 2011 14:45:13 -0500
> > Anthony Liguori wrote:
> >
> >> On 03/14/2011 02:37 PM, Luiz Capitulino wrote:
> >>> qerror_abort() only exists for debugging purposes. I won't sa
On Mon, 14 Mar 2011 15:30:33 -0500
Anthony Liguori wrote:
> On 03/14/2011 03:12 PM, Luiz Capitulino wrote:
> > On Mon, 14 Mar 2011 14:43:48 -0500
> > Anthony Liguori wrote:
> >
> >> On 03/14/2011 02:22 PM, Luiz Capitulino wrote:
> >>> On Fri, 11 Mar 2011 15:00:46 -0600
> >>> Anthony Liguori wr
On 03/14/2011 03:22 PM, Luiz Capitulino wrote:
On Mon, 14 Mar 2011 14:45:13 -0500
Anthony Liguori wrote:
On 03/14/2011 02:37 PM, Luiz Capitulino wrote:
qerror_abort() only exists for debugging purposes. I won't say its perfect,
but it's better than nothing and has already saved some time when
On Mon, 14 Mar 2011 15:18:57 -0500
Anthony Liguori wrote:
> On 03/14/2011 02:25 PM, Luiz Capitulino wrote:
> > On Fri, 11 Mar 2011 15:00:47 -0600
> > Anthony Liguori wrote:
> >
> >> This is a security consideration. We don't want a client to cause an
> >> arbitrary
> >> amount of memory to be
On 03/14/2011 03:12 PM, Luiz Capitulino wrote:
On Mon, 14 Mar 2011 14:43:48 -0500
Anthony Liguori wrote:
On 03/14/2011 02:22 PM, Luiz Capitulino wrote:
On Fri, 11 Mar 2011 15:00:46 -0600
Anthony Liguori wrote:
Not everything handles errors from json parsing gracefully. By at least
resett
On 03/14/2011 02:30 PM, Luiz Capitulino wrote:
libqmp
It's very nice to have client code that convert QMP errors to human
readable strings.
Ok. I'm not sure if I would bother doing this kind of change in this
series (as it's mainly re-working internal stuff) but, this has to be
explained in th
On Mon, 14 Mar 2011 14:34:55 -0500
Anthony Liguori wrote:
> On 03/14/2011 02:18 PM, Luiz Capitulino wrote:
> > On Fri, 11 Mar 2011 15:00:41 -0600
> > Anthony Liguori wrote:
> >
> >> The Error class is similar to QError (now deprecated) except that it
> >> supports
> >> propagation. This allows
On Mon, 14 Mar 2011 14:45:13 -0500
Anthony Liguori wrote:
> On 03/14/2011 02:37 PM, Luiz Capitulino wrote:
> >
> > qerror_abort() only exists for debugging purposes. I won't say its perfect,
> > but it's better than nothing and has already saved some time when writing
> > new errors.
> >
> > I'm
On 03/14/2011 02:25 PM, Luiz Capitulino wrote:
On Fri, 11 Mar 2011 15:00:47 -0600
Anthony Liguori wrote:
This is a security consideration. We don't want a client to cause an arbitrary
amount of memory to be allocated in QEMU. For now, we use a limit of 64MB
which should be large enough for a
Am 14.03.2011 20:23, schrieb Chunqiang Tang:
>>> Here is a detailed description. Relevant to the discussion of
> snapshot,
>>> FVD uses a one-level lookup table and a refcount table. FVD’s
> one-level
>>> lookup table is very similar to QCOW2’s two-level lookup table, except
>
>>> that it is
On Mon, 14 Mar 2011 14:43:48 -0500
Anthony Liguori wrote:
> On 03/14/2011 02:22 PM, Luiz Capitulino wrote:
> > On Fri, 11 Mar 2011 15:00:46 -0600
> > Anthony Liguori wrote:
> >
> >> Not everything handles errors from json parsing gracefully. By at least
> >> resetting the lexer, we'll start gen
On 03/14/2011 02:22 PM, Luiz Capitulino wrote:
On Fri, 11 Mar 2011 15:00:46 -0600
Anthony Liguori wrote:
Not everything handles errors from json parsing gracefully. By at least
resetting the lexer, we'll start generating valid tokens again and hopefully
recover the stream.
Signed-off-by: Ant
On Mon, 14 Mar 2011 14:24:37 -0500
Anthony Liguori wrote:
> On 03/14/2011 02:18 PM, Luiz Capitulino wrote:
> > On Fri, 11 Mar 2011 15:00:42 -0600
> > Anthony Liguori wrote:
> >
> >> These make it very hard to compile QError outside of QEMU.
> > Why would someone do this?
>
> libqmp
>
> It's ve
On 03/14/2011 02:52 PM, Lluís wrote:
Anthony Liguori writes:
I've got a spec written up at http://wiki.qemu.org/Features/QCFG. Initial code
is in my QAPI tree.
What about moving the documentation to a 'doc' attribute?
Thus, instead of the example vnconfig:
{ 'type': 'VncConfig',
'doc': '
On Mon, 14 Mar 2011 14:27:30 -0500
Anthony Liguori wrote:
> On 03/14/2011 02:17 PM, Luiz Capitulino wrote:
> > On Fri, 11 Mar 2011 15:08:38 -0600
> > Anthony Liguori wrote:
> >
> >> On 03/11/2011 03:00 PM, Anthony Liguori wrote:
> >>> This will let Error share the QError human formatting. This
On 03/14/2011 02:18 PM, Luiz Capitulino wrote:
On Fri, 11 Mar 2011 15:00:41 -0600
Anthony Liguori wrote:
The Error class is similar to QError (now deprecated) except that it supports
propagation. This allows for higher quality error handling. It's losely
modeled after glib style GErrors.
I
On Mon, Mar 14, 2011 at 09:20:43PM +0200, Blue Swirl wrote:
> On Mon, Mar 14, 2011 at 3:44 PM, Gleb Natapov wrote:
> > Currently when rogue script kills QEMU process (using TERM/INT/HUP
> > signal) it looks indistinguishable from system shutdown. Lets report
> > that QMEU was killed and leave some
Anthony Liguori writes:
> I've got a spec written up at http://wiki.qemu.org/Features/QCFG. Initial
> code
> is in my QAPI tree.
What about moving the documentation to a 'doc' attribute?
Thus, instead of the example vnconfig:
{ 'type': 'VncConfig',
'doc': 'Configuration options for the buil
On 03/14/2011 02:37 PM, Luiz Capitulino wrote:
qerror_abort() only exists for debugging purposes. I won't say its perfect,
but it's better than nothing and has already saved some time when writing
new errors.
I'm fine dropping it as long as there's a better replacement, which is
not the case he
> > Here is a detailed description. Relevant to the discussion of
snapshot,
> > FVD uses a one-level lookup table and a refcount table. FVD’s
one-level
> > lookup table is very similar to QCOW2’s two-level lookup table, except
> > that it is much smaller in FVD, and is preallocated and hence
On Fri, 11 Mar 2011 15:00:46 -0600
Anthony Liguori wrote:
> Not everything handles errors from json parsing gracefully. By at least
> resetting the lexer, we'll start generating valid tokens again and hopefully
> recover the stream.
>
> Signed-off-by: Anthony Liguori
>
> diff --git a/json-lex
On Fri, 11 Mar 2011 15:00:42 -0600
Anthony Liguori wrote:
> These make it very hard to compile QError outside of QEMU.
Why would someone do this?
>
> Signed-off-by: Anthony Liguori
>
> diff --git a/Makefile.objs b/Makefile.objs
> index da31530..69f0383 100644
> --- a/Makefile.objs
> +++ b/Ma
On Mon, 2011-03-14 at 21:00 +0200, Michael S. Tsirkin wrote:
> On Mon, Mar 14, 2011 at 10:35:08PM +0530, rukhsana ansari wrote:
> > Seeking clarification to the original question I posted:
> > >>
> > >>
> > > This maybe a novice question - Would appreciate it if you can you provide
> > > a
> > > p
On Fri, 11 Mar 2011 15:00:43 -0600
Anthony Liguori wrote:
> Signed-off-by: Anthony Liguori
>
> diff --git a/qerror.c b/qerror.c
> index 78d3884..5a1e637 100644
> --- a/qerror.c
> +++ b/qerror.c
> @@ -109,6 +109,10 @@ static const QErrorStringTable qerror_table[] = {
> .desc = "Dup
On Fri, 11 Mar 2011 15:00:41 -0600
Anthony Liguori wrote:
> The Error class is similar to QError (now deprecated) except that it supports
> propagation. This allows for higher quality error handling. It's losely
> modeled after glib style GErrors.
I think Daniel asked this, but I can't remembe
On 03/14/2011 02:17 PM, Luiz Capitulino wrote:
On Fri, 11 Mar 2011 15:08:38 -0600
Anthony Liguori wrote:
On 03/11/2011 03:00 PM, Anthony Liguori wrote:
This will let Error share the QError human formatting. This is only used for
HMP.
Signed-off-by: Anthony Liguori
diff --git a/qerror.c b/q
On Fri, 11 Mar 2011 15:00:47 -0600
Anthony Liguori wrote:
> This is a security consideration. We don't want a client to cause an
> arbitrary
> amount of memory to be allocated in QEMU. For now, we use a limit of 64MB
> which should be large enough for any reasonably sized token.
>
> This is i
On 03/14/2011 02:18 PM, Luiz Capitulino wrote:
On Fri, 11 Mar 2011 15:00:42 -0600
Anthony Liguori wrote:
These make it very hard to compile QError outside of QEMU.
Why would someone do this?
libqmp
It's very nice to have client code that convert QMP errors to human
readable strings.
Reg
On Tue, Mar 08, 2011 at 04:02:32PM +0200, Gleb Natapov wrote:
> On Tue, Mar 08, 2011 at 07:56:56AM -0600, Anthony Liguori wrote:
> > On 03/08/2011 05:53 AM, Gleb Natapov wrote:
> > >Seabios 0.6.2 is finally released. What about upgrading QEMU to it and
> > >also applying this http://patchwork.ozlab
On Mon, Mar 14, 2011 at 3:44 PM, Gleb Natapov wrote:
> Currently when rogue script kills QEMU process (using TERM/INT/HUP
> signal) it looks indistinguishable from system shutdown. Lets report
> that QMEU was killed and leave some clues about the killed identity.
QEMU ;-)
>
> Signed-off-by: Gleb
On Mon, Mar 14, 2011 at 12:33 PM, Stefan Hajnoczi wrote:
> On Mon, Mar 14, 2011 at 10:23 AM, Peter Maydell
> wrote:
>> On 21 February 2011 08:10, Paolo Bonzini wrote:
>>> On 02/20/2011 06:32 PM, Peter Maydell wrote:
Some of qemu's code does seem to trigger rather excessive memory
use b
On Fri, 11 Mar 2011 15:08:38 -0600
Anthony Liguori wrote:
> On 03/11/2011 03:00 PM, Anthony Liguori wrote:
> > This will let Error share the QError human formatting. This is only used
> > for
> > HMP.
> >
> > Signed-off-by: Anthony Liguori
> >
> > diff --git a/qerror.c b/qerror.c
> > index 4855
On Mon, Mar 14, 2011 at 5:16 PM, Christoph Hellwig wrote:
> On Mon, Mar 14, 2011 at 05:07:57PM +, Stefan Hajnoczi wrote:
>> Hi Christoph,
>> I have written up thoughts on write cache enable, including a
>> workaround to change O_SYNC on a file without kernel changes:
>>
>> http://wiki.qemu.org
On Mon, Mar 14, 2011 at 07:19:29PM +0100, Marco Cianfriglia wrote:
>Hi to alll,
>
> I'm trying to run Windows7 64 on pure qemu-0.14 ( no kvm/xen)
> I compiled qemu with the following : .configure --disable-kvm
> --enable-vnc-thread --target-list=x86_64-softmmu
> Running qemu-system-x86_64
On Mon, Mar 14, 2011 at 10:35:08PM +0530, rukhsana ansari wrote:
> Seeking clarification to the original question I posted:
> >>
> >>
> > This maybe a novice question - Would appreciate it if you can you provide a
> > pointer to documentation or relevant code that explains what is the
> > limitatio
Hi to alll,
I'm trying to run Windows7 64 on pure qemu-0.14 ( no kvm/xen)
I compiled qemu with the following : .configure --disable-kvm
--enable-vnc-thread --target-list=x86_64-softmmu
Running qemu-system-x86_64 -m 2030 -boot c -cdrom /win7_64.iso -hda
win7_64.img
gives me a BS
Am 14.03.2011 17:32, schrieb Chunqiang Tang:
>>> FVD's novel uses of the reference count table reduces the metadata
> update
>>> overhead down to literally zero during normal execution of a VM. This
> gets
>>> the bests of QCOW2's reference count table but without its oeverhead.
> In
>>> FVD, th
On 03/14/2011 11:36 AM, Juan Quintela wrote:
Jes Sorensen wrote:
On 03/14/11 13:14, Juan Quintela wrote:
Please send any agenda items you are interested in covering.
Thanks, Juan.
I presume you mean for March 15? Today is the 14th and it is Monday :)
Dunno what calendar I looked to :p
Yes,
As I've been waiting for QAPI review, I've been working on the design of
a new mechanism to replace our current command line option handling
(QemuOpts) with something that reuses the QAPI infrastructure.
The 'QemuOpts' syntax is just a way to encode complex data structures.
'nic,model=virtio,
Correct the argument and return types for the float<->int conversion helper
functions so that integer arguments and return values are declared as
uint32_t/uint64_t, not float32/float64. This allows us to remove the
hand-rolled functions which were doing bitwise copies between the types
via unions.
On Mon, Mar 14, 2011 at 05:07:57PM +, Stefan Hajnoczi wrote:
> Hi Christoph,
> I have written up thoughts on write cache enable, including a
> workaround to change O_SYNC on a file without kernel changes:
>
> http://wiki.qemu.org/Features/WriteCacheEnable
>
> Guest ability to control write ca
On 03/14/11 17:44, Alon Levy wrote:
> On Mon, Mar 14, 2011 at 04:41:02PM +0100, Jes Sorensen wrote:
>>> +#define MAX_ATR_SIZE 40
>>> +struct EmulatedState {
>>> +CCIDCardState base;
>>> +uint8_t debug;
>>> +char*backend_str;
>>> +uint32_t backend;
>>> +char*cert1;
>>> +
Hi Christoph,
I have written up thoughts on write cache enable, including a
workaround to change O_SYNC on a file without kernel changes:
http://wiki.qemu.org/Features/WriteCacheEnable
Guest ability to control write cache enable is useful and I'd like to
see it in QEMU soon. Any thoughts about w
Seeking clarification to the original question I posted:
>>
>>
> This maybe a novice question - Would appreciate it if you can you provide
a
> pointer to documentation or relevant code that explains what is the
> *limitation in supporting level irq support in kvm irqfd.*
>
>
>
After browsing the KV
On Mon, Mar 14, 2011 at 04:41:02PM +0100, Jes Sorensen wrote:
> On 02/23/11 12:20, Alon Levy wrote:
> > diff --git a/hw/ccid-card-emulated.c b/hw/ccid-card-emulated.c
> > new file mode 100644
> > index 000..bd84d45
> > --- /dev/null
> > +++ b/hw/ccid-card-emulated.c
> > @@ -0,0 +1,599 @@
> > +/
On Mon, Mar 14, 2011 at 04:20:22PM +0100, Jes Sorensen wrote:
ok, here is a note where I kinda ignored my own wishes but I want
to be very clear on them:
libcacard should not be part of qemu.
it is here because I once thought it would speed things up.
So I'm not taking it out or anything - it's
Jes Sorensen wrote:
> On 03/14/11 13:14, Juan Quintela wrote:
>>
>> Please send any agenda items you are interested in covering.
>>
>> Thanks, Juan.
>
> I presume you mean for March 15? Today is the 14th and it is Monday :)
Dunno what calendar I looked to :p
Yes, you are right.
<#secure metho
> > FVD's novel uses of the reference count table reduces the metadata
update
> > overhead down to literally zero during normal execution of a VM. This
gets
> > the bests of QCOW2's reference count table but without its oeverhead.
In
> > FVD, the reference count table is only updated when creati
On Mon, Mar 14, 2011 at 04:50:21PM +0100, Jes Sorensen wrote:
> On 03/14/11 15:52, Alon Levy wrote:
> >> [snip]
> >>> > > +/* VSCMsgInit Client <-> Host
> >>> > > + * Client sends it on connection, with its own capabilities.
> >>> > > + * Host replies with VSCMsgInit filling in its ca
On 03/14/11 15:53, Alon Levy wrote:
> On Mon, Mar 14, 2011 at 03:04:04PM +0100, Jes Sorensen wrote:
>> On 02/23/11 12:20, Alon Levy wrote:
>>> The passthru ccid card is a device sitting on the usb-ccid bus and
>>> using a chardevice to communicate with a remote device using the
>>> VSCard protocol
On 03/14/11 15:52, Alon Levy wrote:
>> [snip]
>>> > > +/* VSCMsgInit Client <-> Host
>>> > > + * Client sends it on connection, with its own capabilities.
>>> > > + * Host replies with VSCMsgInit filling in its capabilities.
>>> > > + *
>>> > > + * It is not meant to be used for negot
Correct the handling of edge cases for the VRECPS instruction:
* this is a Neon instruction so uses the "standard FPSCR value"
* (zero, inf) is a special case which returns 2.0
Signed-off-by: Peter Maydell
---
target-arm/helper.c | 11 ---
1 files changed, 8 insertions(+), 3 deletion
This patchset fixes the edge case handling of VRECPS. Patch 2/2
is just a bit of cleanup of the neighbouring vrsqrts helper which
can then use the float32_two introduced by 1/1.
Tested in the usual random-insn-generation way and also with the
"neon64" test program from the valgrind ARM testsuite.
On 02/23/11 12:20, Alon Levy wrote:
> * add --enable-smartcard and --disable-smartcard flags
> * let the nss check only disable building the ccid-card-emulated device
> * report only if nss is found or not, not smartcard build inclusion
> * don't link with NSS if --disable-smartcard-nss
>
The
On 02/23/11 12:20, Alon Levy wrote:
> Add documentation for the usb-ccid device and accompanying two card
> devices, ccid-card-emulated and ccid-card-passthru.
>
> Signed-off-by: Alon Levy
> ---
> docs/ccid.txt | 135
> +
> 1 files change
On 02/23/11 12:20, Alon Levy wrote:
> diff --git a/hw/ccid-card-emulated.c b/hw/ccid-card-emulated.c
> new file mode 100644
> index 000..bd84d45
> --- /dev/null
> +++ b/hw/ccid-card-emulated.c
> @@ -0,0 +1,599 @@
> +/*
> + * CCID Card Device. Emulated card.
> + *
> + * Copyright (c) 2011 Red Ha
The preferred way to create a constant floating point value is to use
make_float32() rather than doing a runtime int32_to_float32().
Convert the code in the VRSQRTS helper to work this way.
Signed-off-by: Peter Maydell
---
target-arm/helper.c | 11 +--
1 files changed, 5 insertions(+),
On 02/23/11 12:20, Alon Levy wrote:
> +/* private data for PKI applets */
> +typedef struct CACPKIAppletDataStruct {
> +unsigned char *cert;
> +int cert_len;
> +unsigned char *cert_buffer;
> +int cert_buffer_len;
> +unsigned char *sign_buffer;
> +int sign_buffer_len;
> +
Nice that qemu-img convert isn't that far out by default on raw :).
About Google Summer of Code, I have posted my take on applying and
want to share that with you and qemu-devel:
http://blog.vmsplice.net/2011/03/advice-for-students-applying-to-google.html
Thanks for sharing your experience
On 03/14/2011 10:03 AM, Kevin Wolf wrote:
The only problem with them is that they are metadata that must be
updated. However, I think we have discussed enough how to avoid the
greatest part of that cost.
Maybe I missed it, but in the WCE=0 mode, is it really possible to avoid
the writes for the
Am 14.03.2011 15:49, schrieb Anthony Liguori:
> On 03/14/2011 09:21 AM, Kevin Wolf wrote:
>> Am 14.03.2011 15:02, schrieb Anthony Liguori:
>>> On 03/14/2011 08:53 AM, Chunqiang Tang wrote:
> No, because the copy-on-write is another layer on top of the snapshot
> and AFAICT, they don't persi
On Mon, Mar 14, 2011 at 3:04 PM, Chunqiang Tang wrote:
>> >> The file system can keep a lot of these things around pretty easily
> but
>> >> with your proposal, it seems like there can only be one. If you
> support
>> >> many of them, I think you'll degenerate to something as complex as a
>> >> r
Am 14.03.2011 15:47, schrieb Anthony Liguori:
> On 03/14/2011 09:15 AM, Kevin Wolf wrote:
>>> The file system can keep a lot of these things around pretty easily but
>>> with your proposal, it seems like there can only be one. If you support
>>> many of them, I think you'll degenerate to something
On Mon, Mar 14, 2011 at 2:49 PM, Anthony Liguori wrote:
> On 03/14/2011 09:21 AM, Kevin Wolf wrote:
>>
>> Am 14.03.2011 15:02, schrieb Anthony Liguori:
>>>
>>> On 03/14/2011 08:53 AM, Chunqiang Tang wrote:
>
> No, because the copy-on-write is another layer on top of the snapshot
> and
> >> The file system can keep a lot of these things around pretty easily
but
> >> with your proposal, it seems like there can only be one. If you
support
> >> many of them, I think you'll degenerate to something as complex as a
> >> reference count table.
> > IIUC, he already uses a refcount tab
On Mon, Mar 14, 2011 at 03:01:19PM +0100, Jes Sorensen wrote:
> On 02/23/11 12:20, Alon Levy wrote:
> > diff --git a/libcacard/vscard_common.h b/libcacard/vscard_common.h
> > new file mode 100644
> > index 000..7449314
> > --- /dev/null
> > +++ b/libcacard/vscard_common.h
> > @@ -0,0 +1,167 @@
On Mon, Mar 14, 2011 at 03:04:04PM +0100, Jes Sorensen wrote:
> On 02/23/11 12:20, Alon Levy wrote:
> > The passthru ccid card is a device sitting on the usb-ccid bus and
> > using a chardevice to communicate with a remote device using the
> > VSCard protocol defined in libcacard/vscard_common.h
>
On Mon, Mar 14, 2011 at 03:01:19PM +0100, Jes Sorensen wrote:
> On 02/23/11 12:20, Alon Levy wrote:
> > diff --git a/libcacard/vscard_common.h b/libcacard/vscard_common.h
> > new file mode 100644
> > index 000..7449314
> > --- /dev/null
> > +++ b/libcacard/vscard_common.h
> > @@ -0,0 +1,167 @@
On Mon, Mar 14, 2011 at 2:25 PM, Chunqiang Tang wrote:
>> IIUC, he already uses a refcount table. Actually, I think that a
>> refcount table is a requirement to provide the interesting properties
>> that internal snapshots have (see my other mail).
>>
>> Refcount tables aren't a very complex thing
On 03/14/2011 09:21 AM, Kevin Wolf wrote:
Am 14.03.2011 15:02, schrieb Anthony Liguori:
On 03/14/2011 08:53 AM, Chunqiang Tang wrote:
No, because the copy-on-write is another layer on top of the snapshot
and AFAICT, they don't persist when moving between snapshots.
The equivalent for external
> On Mon, Mar 14, 2011 at 1:53 PM, Chunqiang Tang
wrote:
> > Therefore, during normal execution of a
> > VM, images with snapshots are as fast as images without snapshot.
>
> Hang on, an image with a snapshot still needs to do copy-on-write,
> just like backing files. The cost of copy-on-write
On 03/14/2011 09:15 AM, Kevin Wolf wrote:
The file system can keep a lot of these things around pretty easily but
with your proposal, it seems like there can only be one. If you support
many of them, I think you'll degenerate to something as complex as a
reference count table.
IIUC, he already
Am 14.03.2011 15:25, schrieb Chunqiang Tang:
>> IIUC, he already uses a refcount table. Actually, I think that a
>> refcount table is a requirement to provide the interesting properties
>> that internal snapshots have (see my other mail).
>>
>> Refcount tables aren't a very complex thing either. In
> > Your use of "current-state" is confusing me because AFAICT,
> > current-state is just semantically another snapshot.
> >
> > It's writable because it has no children. You only keep around one
> > writable snapshot and to make another snapshot writable, you have to
> > discard the former.
>
On Fri, Mar 11, 2011 at 01:41:17PM -0800, Jordan Justen wrote:
> On Thu, Mar 10, 2011 at 12:21, Gleb Natapov wrote:
> > On Thu, Mar 10, 2011 at 11:50:42AM -0800, Jordan Justen wrote:
> >>
> >> So, perhaps this feature should build upon the other feature you and
> >> Jan are discussing. When will
On Mon, Mar 14, 2011 at 1:53 PM, Chunqiang Tang wrote:
> Therefore, during normal execution of a
> VM, images with snapshots are as fast as images without snapshot.
Hang on, an image with a snapshot still needs to do copy-on-write,
just like backing files. The cost of copy-on-write is reading da
1 - 100 of 148 matches
Mail list logo
