xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Vasiliy Tolstov <v.tolstov@selfip.ru>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Is: events not being cleared during fast migration over InfiniBand Was: Re: xen 4.3 test report
Date: Thu, 6 Jun 2013 10:23:59 +0100	[thread overview]
Message-ID: <51B0552F.1020307@eu.citrix.com> (raw)
In-Reply-To: <20130605185005.GA15558@phenom.dumpdata.com>

On 05/06/13 19:50, Konrad Rzeszutek Wilk wrote:
> On Tue, Jun 04, 2013 at 04:17:55PM +0400, Vasiliy Tolstov wrote:
>> 2013/6/3 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>:
>>> The non-debug version tells me it is:
>>>
>>> 289     if ( (port = get_free_port(d)) < 0 )
>>> 290         ERROR_EXIT(port);
>>>
>>> Which gets -EEXIST from get_free_port. But get_free_port only returns
>>> -EINVAL, -ENOMEM, and -ENOSPC in failure modes.
>>>
>>> But we get -EEXIST? Could you re-run git diff and attach output to
>>> this email? I think you tweaked the debug code a bit so I am looking
>>> at something different?
>>
>> Oh sorry. Yes i modify you patch to this version:
> That is OK.
>> -    if ( v->virq_to_evtchn[virq] != 0 )
>> +    if ( v->virq_to_evtchn[virq] != 0 ) {
>> +       gdprintk(XENLOG_WARNING, "d%dv%d [%s:%d], port:%d, rc:%ld\n",
>> d->domain_id,
>> +               vcpu, __func__,__LINE__, v->virq_to_evtchn[virq],
>> (long)-EEXIST);
>>           ERROR_EXIT(-EEXIST);
> OK, so the value was 3 (event channel), and I am not sure what the virq value
> was. But it looks as if somebody did not clear that and we are
> tripping over it.
>
> George, have you seen issues with events not being cleared during migration?

I haven't, no.  Do you know where the virq is supposed to be clear? The 
BUG() is in restore_cpu_virqs(), but at a quick glance I can't find a 
corresponding function to tear down virqs.

  -George

  reply	other threads:[~2013-06-06  9:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 10:40 xen 4.3 test report Vasiliy Tolstov
2013-05-24 12:46 ` George Dunlap
2013-05-24 13:15   ` Vasiliy Tolstov
2013-05-24 14:11   ` Konrad Rzeszutek Wilk
2013-05-24 14:38     ` George Dunlap
2013-05-24 20:15       ` Vasiliy Tolstov
2013-05-25 11:40         ` Konrad Rzeszutek Wilk
2013-05-27  5:32           ` Vasiliy Tolstov
2013-05-28 15:31             ` Konrad Rzeszutek Wilk
2013-05-28 20:58               ` Vasiliy Tolstov
2013-05-31  4:56           ` Vasiliy Tolstov
2013-06-03 14:08             ` Konrad Rzeszutek Wilk
2013-06-04 12:17               ` Vasiliy Tolstov
2013-06-05 18:50                 ` Is: events not being cleared during fast migration over InfiniBand Was: " Konrad Rzeszutek Wilk
2013-06-06  9:23                   ` George Dunlap [this message]
2013-06-06  9:25                   ` George Dunlap
2013-06-13 11:22                     ` Vasiliy Tolstov
2013-06-13 13:14                       ` Konrad Rzeszutek Wilk
2013-06-13 13:17                         ` Vasiliy Tolstov
2013-06-13 11:24                   ` Vasiliy Tolstov
2013-05-25 11:27       ` Konrad Rzeszutek Wilk
2013-05-24 20:13     ` Vasiliy Tolstov

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=51B0552F.1020307@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=v.tolstov@selfip.ru \
    --cc=xen-devel@lists.xen.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).