escape escape_d9 = { {
- N, N, N, N, N, N, N, I(DstMem16 | Mov, em_fnstcw),
+ I(SrcMem | Stack, em_fld), N, N, I(DstMem | Mov | Stack,
em_fstp), N, N, N, I(DstMem16 | Mov, em_fnstcw),
}, {
/* 0xC0 - 0xC7 */
N, N, N, N, N, N, N, N,
Miltiadi
programs was giving me an illegal instruction based on the
above and it worked by disabling it.
Regards
Milton
On Thu, May 11, 2017 at 2:12 PM, Miltiadis Hatzimihail <
hatzimil...@gmail.com> wrote:
> Ok many thanks for your help.
>
> Milton
>
> On Thu, May 11, 2017 at 2
Ok many thanks for your help.
Milton
On Thu, May 11, 2017 at 2:11 PM, Paolo Bonzini wrote:
>
>
> On 11/05/2017 14:47, Miltiadis Hatzimihail wrote:
> > That's great thanks for the clarification.
> >
> > Is this patch going to make it to the mainline at s
That's great thanks for the clarification.
Is this patch going to make it to the mainline at some point?
Miltiadis Hatzimihail
On Thu, May 11, 2017 at 1:44 PM, Paolo Bonzini wrote:
>
>
> On 11/05/2017 14:40, Miltiadis Hatzimihail wrote:
> > Thanks Paolo that worked!
&g
in the RAM case KVM is not invoked at all.
So for my benefit, does this mean that any RAM transaction is emulated by
QEMU or does it go through KVM to the bare metal? (and hence, KVM is not
emulating this?)
Milton
On Thu, May 11, 2017 at 12:51 PM, Paolo Bonzini wrote:
>
>
> On 11/0
I am trying to develop a simple PCI device and I am setting up 3 BARs. The
last BAR is a DDR and I ve tried 2 different implementations: one
with memory_region_init_io and one with memory_region_init_ram.
I ve got a small program that declares a buffer and does float operations
in the following fa
