[Qemu-devel] Some linux kernel with KAISER/KPTI patch can't work under qemu + haxm.

2018-01-04 Thread lepton
It seems for some reason, some linux kernel with KAISER/KPTI patch can't work with qemu + haxm. The mainline kernel from Linus is fine. But the patch to 4.4/4.10 doesn't work. I am not familiar with HAXM and KPTI either. so not sure if this is a qemu bug or KPTI bug or haxm bug. The same kernel w

Re: [Qemu-devel] [PATCH 1/1] slirp: don't zero ti_i since we acccess it later.

2017-05-08 Thread lepton
r suggestion and will add zero for ih_x1, any comments? On Thu, May 4, 2017 at 4:05 PM, Samuel Thibault wrote: > Hello, > > lepton, on mer. 03 mai 2017 11:35:05 -0700, wrote: > > It sounds like a bug that caller set up a > > right src and dst address and without set right ih

Re: [Qemu-devel] [PATCH 1/1] slirp: don't zero ti_i since we acccess it later.

2017-05-03 Thread lepton
Hi Samuel, Should I add an assert for ih_x1? It sounds like a bug that caller set up a right src and dst address and without set right ih_x1. On Thu, Apr 27, 2017 at 6:21 AM, Samuel Thibault wrote: > Hello, > > Thomas Huth, on lun. 24 avril 2017 11:15:56 +0200, wrote: > > On 20.04.2017 22:43,

[Qemu-devel] I sent out some patch this afternoon it seems it doesn't show here.

2017-04-20 Thread lepton
I sent it several hours ago and they don't show at http://lists.gnu.org/archive/html/qemu-devel/2017-04/index.html Is there some kind of spam filter in this list? I sent those patches with git send-email

[Qemu-devel] [patch]Fix block device read for some SLOW file

2005-07-27 Thread lepton
h will fix it. --- qemu-0.7.1/block.c 2005-07-25 02:52:08.0 +0800 +++ qemu-0.7.1-lepton/block.c 2005-07-27 18:57:21.0 +0800 @@ -591,10 +591,16 @@ static int raw_read(BlockDriverState *bs int ret; lseek(s->fd, sector_num * 512, SEEK_SET); -ret = re