From: "Alex Bennée" <alex.bennee@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 6/6] trace: replace hand-crafted pattern_glob with g_pattern_match_simple
Date: Fri, 06 Dec 2019 11:59:01 +0000 [thread overview]
Message-ID: <87immt7ji2.fsf@linaro.org> (raw)
In-Reply-To: <20191206110354.GA775461@stefanha-x1.localdomain>
Stefan Hajnoczi <stefanha@redhat.com> writes:
> On Thu, Dec 05, 2019 at 12:25:17PM +0000, Alex Bennée wrote:
>> We already use g_pattern_match elsewhere so remove the duplication.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> ---
>> trace/control.c | 35 +----------------------------------
>> 1 file changed, 1 insertion(+), 34 deletions(-)
>
> Is g_pattern_match() a superset of pattern_glob()? Existing patterns
> should continue to work.
Yes - it supports more than pattern_glob and a bit less than the system
glob():
The g_pattern_match* functions match a string against a pattern
containing '*' and '?' wildcards with similar semantics as the standard
glob() function: '*' matches an arbitrary, possibly empty, string, '?'
matches an arbitrary character.
Note that in contrast to glob(), the '/' character can be matched by the
wildcards, there are no '[...]' character ranges and '*' and '?' can not
be escaped to include them literally in a pattern.
If you give me some example existing pattern forms we can add them to
test-logging. I manually tested both single and double * patterns while
working on the rest of the series.
>
> Stefan
--
Alex Bennée
next prev parent reply other threads:[~2019-12-06 16:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 12:25 [PATCH v2 0/6] linux-user mmap debug cleanup Alex Bennée
2019-12-05 12:25 ` [PATCH v2 1/6] linux-user: convert target_mprotect debug to tracepoint Alex Bennée
2019-12-05 15:43 ` Richard Henderson
2019-12-11 14:46 ` Laurent Vivier
2019-12-05 12:25 ` [PATCH v2 2/6] linux-user: convert target_mmap " Alex Bennée
2019-12-05 15:44 ` Richard Henderson
2019-12-11 14:48 ` Laurent Vivier
2019-12-05 12:25 ` [PATCH v2 3/6] linux-user: add target_mmap_complete tracepoint Alex Bennée
2019-12-11 14:48 ` Laurent Vivier
2019-12-05 12:25 ` [PATCH v2 4/6] linux-user: log page table changes under -d page Alex Bennée
2019-12-05 15:45 ` Richard Henderson
2019-12-11 14:53 ` Laurent Vivier
2019-12-05 12:25 ` [PATCH v2 5/6] linux-user: convert target_munmap debug to a tracepoint Alex Bennée
2019-12-11 14:54 ` Laurent Vivier
2019-12-16 12:00 ` Alex Bennée
2019-12-16 12:05 ` Laurent Vivier
2019-12-18 20:03 ` Alex Bennée
2019-12-05 12:25 ` [PATCH v2 6/6] trace: replace hand-crafted pattern_glob with g_pattern_match_simple Alex Bennée
2019-12-05 15:51 ` Richard Henderson
2019-12-06 11:03 ` Stefan Hajnoczi
2019-12-06 11:59 ` Alex Bennée [this message]
2019-12-09 15:58 ` Stefan Hajnoczi
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=87immt7ji2.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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;
as well as URLs for NNTP newsgroup(s).