From: Peter Xu <peterx@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] intel-iommu: start to use error_report_once
Date: Wed, 23 May 2018 09:19:15 +0800 [thread overview]
Message-ID: <20180523011915.GD31932@xz-mi> (raw)
In-Reply-To: <583d5b48-bb34-2c47-8e80-6c1142701506@amsat.org>
On Tue, May 22, 2018 at 06:09:46PM -0300, Philippe Mathieu-Daudé wrote:
> Hi Peter,
>
> On 05/22/2018 12:56 AM, Peter Xu wrote:
> > Replace existing trace_vtd_err() with error_report_once() then stderr
> > will capture something if any of the error happens, meanwhile we don't
> > suffer from any DDOS. Then remove the trace point.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
> > ---
> > hw/i386/intel_iommu.c | 34 +++++++++++++++++-----------------
> > hw/i386/trace-events | 1 -
> > 2 files changed, 17 insertions(+), 18 deletions(-)
> >
> > diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> > index fb31de9416..cf655fb9f6 100644
> > --- a/hw/i386/intel_iommu.c
> > +++ b/hw/i386/intel_iommu.c
> > @@ -285,14 +285,14 @@ static void vtd_generate_fault_event(IntelIOMMUState *s, uint32_t pre_fsts)
> > {
> > if (pre_fsts & VTD_FSTS_PPF || pre_fsts & VTD_FSTS_PFO ||
> > pre_fsts & VTD_FSTS_IQE) {
> > - trace_vtd_err("There are previous interrupt conditions "
> > + error_report_once("There are previous interrupt conditions "
> > "to be serviced by software, fault event "
> > "is not generated.");
>
> Can you keep alignment consistent please?
That was actually intended so reviewers don't need to skim those lines
only caused by indents. If I'm going to touch those lines, then maybe
I can make them even look better by dumping more valid information.
I'll repost. Thanks,
--
Peter Xu
next prev parent reply other threads:[~2018-05-23 1:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 3:56 [Qemu-devel] [PATCH v2 0/2] error-report: introduce {error|warn}_report_once Peter Xu
2018-05-22 3:56 ` [Qemu-devel] [PATCH v2 1/2] qemu-error: " Peter Xu
2018-05-23 15:47 ` Eric Blake
2018-05-24 2:56 ` Peter Xu
2018-05-22 3:56 ` [Qemu-devel] [PATCH v2 2/2] intel-iommu: start to use error_report_once Peter Xu
2018-05-22 21:09 ` Philippe Mathieu-Daudé
2018-05-23 1:19 ` Peter Xu [this message]
2018-05-24 3:40 ` Philippe Mathieu-Daudé
2018-05-22 5:08 ` [Qemu-devel] [PATCH v2 0/2] error-report: introduce {error|warn}_report_once Peter Xu
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=20180523011915.GD31932@xz-mi \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).