On Sun, Nov 29, 2009 at 10:53:40PM +, Natalia Portillo wrote:
> >>
> >We already concluded that "return to PM by triple fault" is not
> >something
> >we want to support. It was needed only on 286 and QEMU doesn't even
> >support 286 cpu emulation.
>
> It is used by a whole kind of operating sy
We already concluded that "return to PM by triple fault" is not
something
we want to support. It was needed only on 286 and QEMU doesn't even
support 286 cpu emulation.
It is used by a whole kind of operating systems (all the 16-bit OS/2
tree) and who knows by how many DOS extenders.
It is
> On 11/29/2009 05:38 PM, Andreas Färber wrote:
>> Am 29.11.2009 um 16:29 schrieb Avi Kivity:
>>> Where is __thread not supported?
>> Apple, Sun.
Some flavours of uClinux :-)
Avi Kivity wrote:
> Well, pthread_getspecific is around 130 bytes of code, whereas __thread
> is just on instruction. Ma
On Sunday 29 November 2009 03:57:37 Filip Navara wrote:
> On Sun, Nov 29, 2009 at 8:00 AM, Rob Landley wrote:
> > On Friday 27 November 2009 05:35:26 Filip Navara wrote:
> >> On Fri, Nov 27, 2009 at 12:17 PM, Vincent Sanders
> >
> > wrote:
> >> > I appear to be unable to take a hint, your silence
"Michael S. Tsirkin" wrote:
> On Thu, Nov 26, 2009 at 07:33:02PM +0100, Juan Quintela wrote:
>> "Michael S. Tsirkin" wrote:
>> > Hi!
>> > qemu build on fedora 10 fails with:
>> > /root/scm/qemu/fpu/softfloat-native.c:132:5: error: "HOST_LONG_BITS" is
>> > not defined
>> > make[1]: *** [fpu/softf
On Sun, 29 Nov 2009, Andreas Färber wrote:
I.e. if unavoidable, instead of #define PSR_XXX 123 one might need to #define
TARGET_PSR_XXX 123 and change *all* uses of PSR_XXX to TARGET_PSR_XXX, so
that Sun's and QEMU's definitions can live side by side. If your approach or
#undef works correctly
Am 29.11.2009 um 15:17 schrieb Andreas Färber:
Am 14.06.2009 um 00:15 schrieb Andreas Färber:
Am 31.05.2009 um 12:15 schrieb Anthony Liguori:
Starting with this commit, qemu-system-sparc segfaults
immediately;
you later fixed it in c833ab7351f2ebac46740380a81e34482e208dcc
(Fix
segv when
Glauber Costa wrote:
> Hi guys,
>
> This is an early version of smp support in kvm that kinda works.
> It has some known problems that I am still tracking. For example,
> it does not reset very well. Also, initialization is a bit slow,
> probably because of the number of remote ioctl calls involve
Am 29.11.2009 um 16:42 schrieb Avi Kivity:
On 11/29/2009 05:38 PM, Andreas Färber wrote:
Am 29.11.2009 um 16:29 schrieb Avi Kivity:
On 11/26/2009 07:24 PM, Glauber Costa wrote:
Since we'll have multiple cpu threads, at least for kvm, we need
a way to store
and retrieve the CPUState associ
On 11/29/2009 05:38 PM, Andreas Färber wrote:
Am 29.11.2009 um 16:29 schrieb Avi Kivity:
On 11/26/2009 07:24 PM, Glauber Costa wrote:
Since we'll have multiple cpu threads, at least for kvm, we need a
way to store
and retrieve the CPUState associated with the current execution thread.
For th
Am 29.11.2009 um 16:29 schrieb Avi Kivity:
On 11/26/2009 07:24 PM, Glauber Costa wrote:
Since we'll have multiple cpu threads, at least for kvm, we need a
way to store
and retrieve the CPUState associated with the current execution
thread.
For the I/O thread, this will be NULL.
I am using
On 11/26/2009 07:24 PM, Glauber Costa wrote:
This fix a bug with -smp in kvm. Since we have updated apic_base,
we also have to tell kernel about it. So instead of just updating
mp_state, update every regs.
Signed-off-by: Glauber Costa
---
hw/apic-kvm.c |5 -
1 files changed, 4 inserti
On 11/26/2009 07:24 PM, Glauber Costa wrote:
This function is similar to qemu-kvm's on_vcpu mechanism. Totally synchronous,
and guarantees that a given function will be executed at the specified vcpu.
The approach I am taking is to put it under the hood, in kvm_vcpu_ioctl.
This way, the kvm_vcpu
On 11/26/2009 07:24 PM, Glauber Costa wrote:
Since we'll have multiple cpu threads, at least for kvm, we need a way to store
and retrieve the CPUState associated with the current execution thread.
For the I/O thread, this will be NULL.
I am using pthread functions for that, for portability, but
Am 29.11.2009 um 13:34 schrieb Palle Lyckegaard:
On Sun, 29 Nov 2009, Andreas Färber wrote:
Not having that v7 dir on amd64 here, did you check whether their
values are really defined identically?
If not, it may be necessary to either #undef them first or to
prefix them with TARGET_ as d
Hello,
Am 14.06.2009 um 00:15 schrieb Andreas Färber:
Am 31.05.2009 um 12:15 schrieb Anthony Liguori:
Starting with this commit, qemu-system-sparc segfaults
immediately;
you later fixed it in c833ab7351f2ebac46740380a81e34482e208dcc
(Fix
segv when passing an unknown protocol) to no longer
On Sun, 29 Nov 2009, Andreas Färber wrote:
Not having that v7 dir on amd64 here, did you check whether their values are
really defined identically?
If not, it may be necessary to either #undef them first or to prefix them
with TARGET_ as done for the user emulators...
In which files are T
Hello,
Am 27.10.2009 um 18:38 schrieb malc:
On Tue, 27 Oct 2009, Markus Armbruster wrote:
Mark McLoughlin writes:
On Thu, 2009-10-01 at 09:42 -0500, Justin M. Forbes wrote:
Author: Justin M. Forbes
Date: Thu Oct 1 09:34:56 2009 -0500
Improve error reporting on file access
By ma
On Thu, Nov 26, 2009 at 07:33:02PM +0100, Juan Quintela wrote:
> "Michael S. Tsirkin" wrote:
> > Hi!
> > qemu build on fedora 10 fails with:
> > /root/scm/qemu/fpu/softfloat-native.c:132:5: error: "HOST_LONG_BITS" is not
> > defined
> > make[1]: *** [fpu/softfloat-native.o] Error 1
> > make: ***
On Thu, Nov 26, 2009 at 07:54:43PM +0100, Juan Quintela wrote:
> "Michael S. Tsirkin" wrote:
> > This rearranges code in preparation for interrupt state
> > implementation.
> > Changes:
> > - split up but walk away from interrupt handling
> > into a subroutine
> > - change irq_st
On 11/21/2009 02:47 AM, Kevin O'Connor wrote:
Can you retry this with the latest seabios git. If you are able to
reproduce, can you set CONFIG_DEBUG_LEVEL to 8 and post the log?
Maybe something in the log will help.
With current seabios.git the problem is resolved.
--
error compiling com
On Fri, Nov 27, 2009 at 01:25:36PM +0100, Kevin Wolf wrote:
> Either rename variables and functions to refer to write errors (which is what
> they actually do) or introduce a parameter to distinguish reads and writes.
>
I prefer either to use two different functions or hide 0/1 parameter behind
a
On Sun, Nov 29, 2009 at 8:00 AM, Rob Landley wrote:
> On Friday 27 November 2009 05:35:26 Filip Navara wrote:
>> On Fri, Nov 27, 2009 at 12:17 PM, Vincent Sanders
> wrote:
>> > I appear to be unable to take a hint, your silence on this patch in
>> > the past probably ought to have been a clue. ho
On Fri, Nov 27, 2009 at 09:42:19PM +0100, Sebastian Herbszt wrote:
> Gleb Natapov wrote:
> >On Thu, Nov 26, 2009 at 09:55:28PM +0100, Sebastian Herbszt wrote:
> >>Gleb Natapov wrote:
> >>>On Wed, Nov 25, 2009 at 11:04:20PM +0100, Sebastian Herbszt wrote:
> Gleb Natapov wrote:
> >On Wed, Nov
24 matches
Mail list logo
