From: Asias He <asias.hejun@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Pekka Enberg <penberg@kernel.org>,
gorcunov@gmail.com, prasadjoshi124@gmail.com,
kvm@vger.kernel.org
Subject: Re: [PATCH 3/4] kvm tools: Add debug feature to test the IO thread
Date: Wed, 20 Apr 2011 07:10:18 +0800 [thread overview]
Message-ID: <4DAE165A.3070404@gmail.com> (raw)
In-Reply-To: <20110419171116.GD6640@elte.hu>
On 04/20/2011 01:11 AM, Ingo Molnar wrote:
>
> * Sasha Levin <levinsasha928@gmail.com> wrote:
>
>> On Tue, 2011-04-19 at 19:52 +0300, Pekka Enberg wrote:
>>> On Mon, Apr 18, 2011 at 4:02 PM, Sasha Levin <levinsasha928@gmail.com> wrote:
>>>> Add --debug-io-delay-cycles and --debug-io-delay-amount to delay the completion of IO requests within virtio-blk.
>>>> This feature allows to verify and debug the threading within virtio-blk.
>>>>
>>>> Signed-off-by: Sasha Levin <levinsasha928@gmail.com>
>>>
>>> Well, to be honest, I'm not convinced we need both of these. Isn't
>>> --debug-io-delay=<msec> enough for our use?
>>
>> This came up during our testing.
>>
>> Ingo suggested a large delay so we could easily see the results of
>> threading. The problem we encountered was that having a delay right from
>> the beginning will make the guest kernel take a rather long time to boot
>> and would make actually testing the threading impossible.
>>
>> I've added a delay before the activation of the I/O request completion
>> delay to give the tester/debugger enough time to boot into the guest and
>> prepare anything needed for the test.
>>
>> Making it a constant is also rather hard because different kernels can
>> take a very different amount of I/O requests to boot. Take the simple
>> example of a whether fsck was running during the boot or not.
>
> I suspect we'll eventually want to have some sort of 'kvm set' subcommand that
> can modify attributes of running instances? Setting the debug delay would be
> one of the options:
>
> kvm set MyInstance-1 --debug-io-delay-ms 10000
>
> That way the delay can be activated in a suitable moment - and disabled again
> after testing:
>
> kvm set MyInstance-1 --debug-io-delay-ms 0
>
It's a very good idea.
Do we need:
kvm get MyInstance-1
which reports all the attributes, or
kvm get MyInstance-1 --debug-io-delay-ms
which only reports the interested attribute.
--
Best Regards,
Asias He
next prev parent reply other threads:[~2011-04-19 23:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 13:02 [PATCH 1/4] kvm tools: Thread virtio-blk Sasha Levin
2011-04-18 13:02 ` [PATCH 2/4] kvm tools: Use virtio_blk_parameters to configure virtio-blk Sasha Levin
2011-04-18 13:02 ` [PATCH 3/4] kvm tools: Add debug feature to test the IO thread Sasha Levin
2011-04-19 16:52 ` Pekka Enberg
2011-04-19 17:04 ` Sasha Levin
2011-04-19 17:11 ` Ingo Molnar
2011-04-19 23:10 ` Asias He [this message]
2011-04-20 5:41 ` Pekka Enberg
2011-04-20 8:54 ` Ingo Molnar
2011-04-18 13:02 ` [PATCH 4/4] kvm tools: Complete missing segments in a iov op using regular op Sasha Levin
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=4DAE165A.3070404@gmail.com \
--to=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.com \
/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