On 2020/6/3 下午2:34, Michael S. Tsirkin wrote:
On Wed, Jun 03, 2020 at 12:18:44PM +0800, Jason Wang wrote:
On 2020/6/2 下午9:31, Michael S. Tsirkin wrote:
On Tue, Jun 02, 2020 at 02:49:38PM +0800, Jason Wang wrote:
On 2020/6/2 下午12:56, Michael S. Tsirkin wrote:
On Tue, Jun 02, 2020 at 03:22:49A
On Wed, Jun 03, 2020 at 12:18:44PM +0800, Jason Wang wrote:
>
> On 2020/6/2 下午9:31, Michael S. Tsirkin wrote:
> > On Tue, Jun 02, 2020 at 02:49:38PM +0800, Jason Wang wrote:
> > > On 2020/6/2 下午12:56, Michael S. Tsirkin wrote:
> > > > On Tue, Jun 02, 2020 at 03:22:49AM +0800, kbuild test robot wro
On 2020/6/2 下午9:31, Michael S. Tsirkin wrote:
On Tue, Jun 02, 2020 at 02:49:38PM +0800, Jason Wang wrote:
On 2020/6/2 下午12:56, Michael S. Tsirkin wrote:
On Tue, Jun 02, 2020 at 03:22:49AM +0800, kbuild test robot wrote:
Hi Jason,
I love your patch! Yet something to improve:
[auto build test
On Tue, Jun 02, 2020 at 02:49:38PM +0800, Jason Wang wrote:
>
> On 2020/6/2 下午12:56, Michael S. Tsirkin wrote:
> > On Tue, Jun 02, 2020 at 03:22:49AM +0800, kbuild test robot wrote:
> > > Hi Jason,
> > >
> > > I love your patch! Yet something to improve:
> > >
> > > [auto build test ERROR on vho
On 2020/6/2 下午12:56, Michael S. Tsirkin wrote:
On Tue, Jun 02, 2020 at 03:22:49AM +0800, kbuild test robot wrote:
Hi Jason,
I love your patch! Yet something to improve:
[auto build test ERROR on vhost/linux-next]
[also build test ERROR on linus/master v5.7 next-20200529]
[if your patch is app
On Tue, Jun 02, 2020 at 03:22:49AM +0800, kbuild test robot wrote:
> Hi Jason,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on vhost/linux-next]
> [also build test ERROR on linus/master v5.7 next-20200529]
> [if your patch is applied to the wrong git tree, please dr
On 2020/5/30 上午2:30, Rob Miller wrote:
Given the need for 4K doorbell such that QEMU can easily map, ect, and
assuming that I have a HW device which exposes 2 VQ's, with a
notification area off of BAR3, offset=whatever, notifier_multiplier=4,
we don't need to have 2 x 4K pages mapped into the
Hi Jason,
I love your patch! Yet something to improve:
[auto build test ERROR on vhost/linux-next]
[also build test ERROR on linus/master v5.7 next-20200529]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' opt
Given the need for 4K doorbell such that QEMU can easily map, ect, and
assuming that I have a HW device which exposes 2 VQ's, with a notification
area off of BAR3, offset=whatever, notifier_multiplier=4, we don't need to
have 2 x 4K pages mapped into the VM for both doorbells do we? The guest
drive
On 2020/5/29 下午5:16, Mika Penttilä wrote:
Hi,
On 29.5.2020 11.03, Jason Wang wrote:
Currently the doorbell is relayed via eventfd which may have
significant overhead because of the cost of vmexits or syscall. This
patch introduces mmap() based doorbell mapping which can eliminate the
overhead
Currently the doorbell is relayed via eventfd which may have
significant overhead because of the cost of vmexits or syscall. This
patch introduces mmap() based doorbell mapping which can eliminate the
overhead caused by vmexit or syscall.
To ease the userspace modeling of the doorbell layout (usua
11 matches
Mail list logo
