Linux virtualization list
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: zhaoguohan@kylinos.cn
Cc: virtualization@lists.linux.dev,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH 2/2] tools/virtio: add a vhost dirty log test
Date: Thu, 12 Nov 2026 09:08:52 +0000	[thread overview]
Message-ID: <sashiko-outbox-210827@kernel.org> (raw)
In-Reply-To: <20261112085631.128819-3-zhaoguohan@kylinos.cn>

> From: Khan Zhao <zhaoguohan@kylinos.cn>
> 
> Add vhost_log_test, which exercises used-ring dirty logging through the
> existing vhost_test module. It sets a log base with VHOST_SET_LOG_BASE,
> enables VHOST_VRING_F_LOG on the ring, submits descriptors and checks
> the resulting bitmap from userspace. No new kernel interface is needed.
> 
> The test covers:
> 
>  - every bit in a byte, repeated sets, and neighbouring bytes being left
>    untouched, including the last byte of a page followed by a PROT_NONE
>    guard page
>  - a log page that has not been faulted in yet, read-only, PROT_NONE
>    and unmapped log pages, and logging after access is restored
>  - private (COW) and shared file mappings, checking that the bit reaches
> [ ... ]
> A --bench mode reports ns per descriptor with logging disabled and
> enabled. vhost_log_test.rst describes how to build and run the test.
> 
> Assisted-by: Codex:gpt-6.1-sol
> Signed-off-by: Khan Zhao <zhaoguohan@kylinos.cn>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261112085631.128819-1-zhaoguohan@kylinos.cn?part=2


      reply	other threads:[~2026-11-12  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  8:56 [PATCH 0/2] vhost: set dirty log bits without pinning pages on x86 zhaoguohan
2026-11-12  8:56 ` [PATCH 1/2] " zhaoguohan
2026-11-12  9:08   ` sashiko-bot
2026-11-12  9:15   ` Michael S. Tsirkin
2026-11-12  8:56 ` [PATCH 2/2] tools/virtio: add a vhost dirty log test zhaoguohan
2026-11-12  9:08   ` sashiko-bot [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=sashiko-outbox-210827@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=eperezma@redhat.com \
    --cc=mst@redhat.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=virtualization@lists.linux.dev \
    --cc=zhaoguohan@kylinos.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox