search for: accelreality

On 2019/9/5 ??9:59, Jason Gunthorpe wrote: > On Thu, Sep 05, 2019 at 08:27:34PM +0800, Jason Wang wrote: >> Hi: >> >> Per request from Michael and Jason, the metadata accelreation is >> reverted in this version and rework in next version. >> >> Please review. >> >> Thanks >> >> Jason Wang (2): >> Revert "vhost: access vq

On 2019/9/5 ??9:59, Jason Gunthorpe wrote: > On Thu, Sep 05, 2019 at 08:27:34PM +0800, Jason Wang wrote: >> Hi: >> >> Per request from Michael and Jason, the metadata accelreation is >> reverted in this version and rework in next version. >> >> Please review. >> >> Thanks >> >> Jason Wang (2): >> Revert "vhost: access vq

From: Jason Wang <jasowang at redhat.com> Date: Wed, 7 Aug 2019 03:06:08 -0400 > This series try to fix several issues introduced by meta data > accelreation series. Please review. ... My impression is that patch #7 will be changed to use spinlocks so there will be a v5.

On Thu, Sep 05, 2019 at 08:27:34PM +0800, Jason Wang wrote: > Hi: > > Per request from Michael and Jason, the metadata accelreation is > reverted in this version and rework in next version. > > Please review. > > Thanks > > Jason Wang (2): > Revert "vhost: access vq metadata through kernel virtual address" > vhost: re-introducing metadata

On Fri, Sep 06, 2019 at 06:02:35PM +0800, Jason Wang wrote: > > On 2019/9/5 ??9:59, Jason Gunthorpe wrote: > > On Thu, Sep 05, 2019 at 08:27:34PM +0800, Jason Wang wrote: > > > Hi: > > > > > > Per request from Michael and Jason, the metadata accelreation is > > > reverted in this version and rework in next version. > > > > > >

From: Jason Wang <jasowang at redhat.com> Date: Fri, 6 Sep 2019 18:02:35 +0800 > On 2019/9/5 ??9:59, Jason Gunthorpe wrote: >> I think you should apply the revert this cycle and rebase the other >> patch for next.. >> >> Jason > > Yes, the plan is to revert in this release cycle. Then you should reset patch #1 all by itself targetting 'net'.

On 2019/9/6 ??9:15, David Miller wrote: > From: Jason Wang <jasowang at redhat.com> > Date: Fri, 6 Sep 2019 18:02:35 +0800 > >> On 2019/9/5 ??9:59, Jason Gunthorpe wrote: >>> I think you should apply the revert this cycle and rebase the other >>> patch for next.. >>> >>> Jason >> Yes, the plan is to revert in this release cycle. >

...y get crashed. and try to boot domU as hvm builder = "hvm" the iso booted very well, but report i686 cpu detected. I''m running on an Intel Core 2 E7500 CPU , and VT-x is turned on. I''m confused. Someone could help me out, thanks! -- Silence is golden. twitter: @AccelReality wikipedia: AleiPhoenix blog: weblog.areverie.org wiki: wiki.areverie.org _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

On 2019/8/11 ??1:52, Michael S. Tsirkin wrote: > On Fri, Aug 09, 2019 at 01:48:42AM -0400, Jason Wang wrote: >> Hi all: >> >> This series try to fix several issues introduced by meta data >> accelreation series. Please review. >> >> Changes from V4: >> - switch to use spinlock synchronize MMU notifier with accessors >> >> Changes from V3:

On 2019/8/11 ??1:52, Michael S. Tsirkin wrote: > On Fri, Aug 09, 2019 at 01:48:42AM -0400, Jason Wang wrote: >> Hi all: >> >> This series try to fix several issues introduced by meta data >> accelreation series. Please review. >> >> Changes from V4: >> - switch to use spinlock synchronize MMU notifier with accessors >> >> Changes from V3:

Hi all: This series try to fix several issues introduced by meta data accelreation series. Please review. Changes from V3: - remove the unnecessary patch Changes from V2: - use seqlck helper to synchronize MMU notifier with vhost worker Changes from V1: - try not use RCU to syncrhonize MMU notifier with vhost worker - set dirty pages after no readers - return -EAGAIN only when we find the

Hi all: This series try to fix several issues introduced by meta data accelreation series. Please review. Changes from V3: - remove the unnecessary patch Changes from V2: - use seqlck helper to synchronize MMU notifier with vhost worker Changes from V1: - try not use RCU to syncrhonize MMU notifier with vhost worker - set dirty pages after no readers - return -EAGAIN only when we find the

Hi all: This series try to fix several issues introduced by meta data accelreation series. Please review. Changes from V2: - use seqlck helper to synchronize MMU notifier with vhost worker Changes from V1: - try not use RCU to syncrhonize MMU notifier with vhost worker - set dirty pages after no readers - return -EAGAIN only when we find the range is overlapped with metadata Jason Wang (9):

On Mon, Aug 12, 2019 at 05:49:08AM -0400, Michael S. Tsirkin wrote: > On Mon, Aug 12, 2019 at 10:44:51AM +0800, Jason Wang wrote: > > > > On 2019/8/11 ??1:52, Michael S. Tsirkin wrote: > > > On Fri, Aug 09, 2019 at 01:48:42AM -0400, Jason Wang wrote: > > > > Hi all: > > > > > > > > This series try to fix several issues introduced by

On Mon, Aug 12, 2019 at 05:49:08AM -0400, Michael S. Tsirkin wrote: > On Mon, Aug 12, 2019 at 10:44:51AM +0800, Jason Wang wrote: > > > > On 2019/8/11 ??1:52, Michael S. Tsirkin wrote: > > > On Fri, Aug 09, 2019 at 01:48:42AM -0400, Jason Wang wrote: > > > > Hi all: > > > > > > > > This series try to fix several issues introduced by

On Fri, Aug 09, 2019 at 01:48:42AM -0400, Jason Wang wrote: > Hi all: > > This series try to fix several issues introduced by meta data > accelreation series. Please review. > > Changes from V4: > - switch to use spinlock synchronize MMU notifier with accessors > > Changes from V3: > - remove the unnecessary patch > > Changes from V2: > - use seqlck

On Mon, Aug 12, 2019 at 10:44:51AM +0800, Jason Wang wrote: > > On 2019/8/11 ??1:52, Michael S. Tsirkin wrote: > > On Fri, Aug 09, 2019 at 01:48:42AM -0400, Jason Wang wrote: > > > Hi all: > > > > > > This series try to fix several issues introduced by meta data > > > accelreation series. Please review. > > > > > > Changes from

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As stated by your message, I''ll try it again on the mailing list.. I tried your wondershaper today and there is one thing I am puzzling about. If I add port 80 and 21 like this NOPRIOPORTSRC=''80 21'' The uploads from my webserver and ftp server are a lot faster then without adding the ports and surfing the web is a pain. If

...el and ramdisk file just located in /boot The docs didn''t help much. http://xenbits.xen.org/docs/unstable/misc/efi.html So... Where should I put the xen-4.2.2.efi and the corresponding config file into ? How should I configure the efibootmgr ? Thanks. -- Silence is golden. twitter: @AccelReality wikipedia: AleiPhoenix blog: weblog.areverie.org wiki: wiki.areverie.org _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users

On Tue, Aug 20, 2019 at 10:29:32AM +0800, Jason Wang wrote: > > On 2019/8/20 ??5:08, Michael S. Tsirkin wrote: > > On Tue, Aug 13, 2019 at 04:12:49PM +0800, Jason Wang wrote: > > > On 2019/8/12 ??5:49, Michael S. Tsirkin wrote: > > > > On Mon, Aug 12, 2019 at 10:44:51AM +0800, Jason Wang wrote: > > > > > On 2019/8/11 ??1:52, Michael S. Tsirkin