From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Bruce Rogers <brogers@suse.com>, qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org, anthony.perard@citrix.com
Subject: Re: [Qemu-devel] [PATCH for-2.7] Xen PCI passthrough: fix passthrough failure when no interrupt pin
Date: Thu, 28 Jul 2016 11:10:48 +0800 [thread overview]
Message-ID: <579977B8.4090600@cn.fujitsu.com> (raw)
In-Reply-To: <1469633448-10692-1-git-send-email-brogers@suse.com>
hello bruce,
AFAIK, the message in error object will be printed to stderr or current
monitor according whether we have a monitor. I just checked XEN_PT_LOG,
message is only printed to stderr. If Xen pt device can be hotplugged
via monitor command device_add, I guess using error object is right.
Yours Sincerely,
Cao jin
On 07/27/2016 11:30 PM, Bruce Rogers wrote:
> Commit 5a11d0f7 mistakenly converted a log message into an error
> condition when no pin interrupt is found for the pci device being
> passed through. Revert that part of the commit.
>
> Signed-off-by: Bruce Rogers <brogers@suse.com>
> ---
> hw/xen/xen_pt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c
> index f593b04..b6d71bb 100644
> --- a/hw/xen/xen_pt.c
> +++ b/hw/xen/xen_pt.c
> @@ -842,7 +842,7 @@ static void xen_pt_realize(PCIDevice *d, Error **errp)
> goto err_out;
> }
> if (!scratch) {
> - error_setg(errp, "no pin interrupt");
> + XEN_PT_LOG(d, "no pin interrupt\n");
> goto out;
> }
>
>
next prev parent reply other threads:[~2016-07-28 3:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 15:30 [Qemu-devel] [PATCH for-2.7] Xen PCI passthrough: fix passthrough failure when no interrupt pin Bruce Rogers
2016-07-28 3:10 ` Cao jin [this message]
2016-08-01 17:17 ` Bruce Rogers
2016-08-04 2:51 ` Cao jin
2016-08-04 14:08 ` Anthony PERARD
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=579977B8.4090600@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=anthony.perard@citrix.com \
--cc=brogers@suse.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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.