On Thu, 16 Aug 2012 14:45:15 -0400 (EDT)
Tomas Racek wrote:
> - Original Message -
> > On Thu, Aug 16, 2012 at 09:35:12AM -0400, Tomas Racek wrote:
> > > Hi,
> > >
> > > I am writing a file system test which I execute in qemu with kernel
> > > compiled from latest git sources and running
> >register_pio_hook_ptr_r(PIO_IDE, SIZE_BYTE,&s->cmd[0]);
> >for (i = 1; i< 7; i++) {
> > register_pio_hook_ptr_r(PIO_IDE + i, SIZE_BYTE,&s->cmd[i]);
> > register_pio_hook_ptr_w(PIO_IDE + i, SIZE_BYTE,&s->cmd[i]);
> >}
>
> You can't easily serialize updates to that address
> If the fd overhead really is a problem, perhaps the fd could be retained
> for setup operations, and omitted only on calls that require a vcpu to
> have been already set up on the current thread?
Quite frankly I'd like to have an fd because it means you've got a
meaningful way of ensuring that i
> Well on real hardware, the instruction rate and the timer are linked:
> the timer run at half the speed of the CPU. As the corresponding
> assembly code is very small, only uses registers and is run in kernel
> mode, you know for sure that 48 cycles is more than enough.
What happens on NMI or if
