From: Peter Lieven <pl@kamp.de>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH V4] block/nfs: add support for setting debug level
Date: Fri, 06 Nov 2015 12:25:18 +0100 [thread overview]
Message-ID: <563C8E1E.9030908@kamp.de> (raw)
In-Reply-To: <20151106112339.GG12285@stefanha-x1.localdomain>
Am 06.11.2015 um 12:23 schrieb Stefan Hajnoczi:
> On Thu, Nov 05, 2015 at 11:25:34PM +0100, Peter Lieven wrote:
>> recent libnfs versions support logging debug messages. Add
>> support for it in qemu through an URL parameter.
>>
>> Example:
>> qemu -cdrom nfs://127.0.0.1/iso/my.iso?debug=2
>> ---
>> v3->v4: revert to the initial version, but limit max debug level
>> v2->v3: use a per-drive option instead of a global one. [Stefan]
>> v1->v2: reworked patch to accept the debug level as a cmdline
>> parameter instead of an URI parameter [Stefan]
>>
>> block/nfs.c | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/block/nfs.c b/block/nfs.c
>> index fd79f89..fbea25a 100644
>> --- a/block/nfs.c
>> +++ b/block/nfs.c
>> @@ -36,6 +36,7 @@
>> #include <nfsc/libnfs.h>
>>
>> #define QEMU_NFS_MAX_READAHEAD_SIZE 1048576
>> +#define QEMU_NFS_MAX_DEBUG_LEVEL 2
>>
>> typedef struct NFSClient {
>> struct nfs_context *context;
>> @@ -334,6 +335,15 @@ static int64_t nfs_client_open(NFSClient *client, const char *filename,
>> }
>> nfs_set_readahead(client->context, val);
>> #endif
>> +#ifdef LIBNFS_FEATURE_DEBUG
>> + } else if (!strcmp(qp->p[i].name, "debug")) {
>> + if (val > QEMU_NFS_MAX_DEBUG_LEVEL) {
>> + error_report("NFS Warning: Limiting NFS debug level"
>> + " to %d", QEMU_NFS_MAX_DEBUG_LEVEL);
>> + val = QEMU_NFS_MAX_DEBUG_LEVEL;
>> + }
>> + nfs_set_debug(client->context, val);
>> +#endif
> Please include the rationale for limiting the debug level as a comment
> in the code. Otherwise people may read the code and not understand why
> we do this.
Okay. Then we should add this to the readahead limitation as well.
>
> The error message should indicate how to set high debug levels (if
> possible). A simple "You can't do that" error message is frustrating
> :).
But thats the case at the moment ;-)
Peter
prev parent reply other threads:[~2015-11-06 11:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 22:25 [Qemu-devel] [PATCH V4] block/nfs: add support for setting debug level Peter Lieven
2015-11-06 11:23 ` Stefan Hajnoczi
2015-11-06 11:25 ` Peter Lieven [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=563C8E1E.9030908@kamp.de \
--to=pl@kamp.de \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.