search for: offset16

On Tue, 2014-01-14 at 22:59 -0800, Craig Topper wrote: > I started trying to fix this tonight but it's pretty nasty to fix. > I'll try to make another go at it later this week. Much of it seems fixed already; what's left to fix? The segment prefix override? Does that mean we get to fix disassembly of '0x65 0xa4' while we're at it? (Although we can't even

I believe I have now fixed the 0x64 0xa1 0x00 0x00 0x00 0x00 bug in r199364. On Wed, Jan 15, 2014 at 10:53 AM, Craig Topper <craig.topper at gmail.com>wrote: > To fix it we need to change offset8/offset16/etc to have two suboperands > and update the printer to understand that. Also update the disassembler to > add the segment to the MCInst when its creating it. When I did these two > things the MCCodeEmitter broke because it tried to interpret the extra > operand as an immediate. I think...

...er than relying on an implementation-specific bus to back this up. - Make virtio_config_ops much higher-level, don't assume layout of config space. - Expose "struct virtqueue" again and move ops inside that. - virtio_ring uses 64 bit address, 32 bit length, not addr64 + offset16 + len16. - flags in virtio_ring to allow suppression of interrupts (by guest) or notifications (by host). I'm not too unhappy with this as it stands. Feedback welcome! Cheers, Rusty.

...er than relying on an implementation-specific bus to back this up. - Make virtio_config_ops much higher-level, don't assume layout of config space. - Expose "struct virtqueue" again and move ops inside that. - virtio_ring uses 64 bit address, 32 bit length, not addr64 + offset16 + len16. - flags in virtio_ring to allow suppression of interrupts (by guest) or notifications (by host). I'm not too unhappy with this as it stands. Feedback welcome! Cheers, Rusty.