All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: hvm_set_callback_irq_level() deadlock?
Date: Wed, 07 Jan 2009 19:22:29 +0900	[thread overview]
Message-ID: <49648265.6070808@jp.fujitsu.com> (raw)
In-Reply-To: <C58A2D6B.20CF5%keir.fraser@eu.citrix.com>

Hi,

Keir Fraser wrote:
> On 07/01/2009 09:41, "Akio Takebe" <takebe_akio@jp.fujitsu.com> wrote:
> 
>> hvm_set_callback_irq_level() and so on call vioapic_irq_positive_edge()
>> before spin_unlock(&d->arch.hvm_domain.irq_lock).
>> I think it cause a deadlock.
>> If it is right, how should we fix them?
>> What do you think?
> 
> Doesn't vioapic_irq_positive_edge() clearly expect to be called with that
> lock held?
I concern about that vioapic_deliver() calls vcpu_kick(). If vcpu0 has the lock and
vcpu1 cannot get lock and spin then vcpu0 sleep in another function,
it may cause deadlock because vioapic_irq_positive_edge() may call vcpu_kick().
For example, the following function is OK?

1087 static void time_calibration_rendezvous(void *_r)
1088 {
1089     struct cpu_calibration *c = &this_cpu(cpu_calibration);
1090     struct calibration_rendezvous *r = _r;
1091     unsigned int total_cpus = cpus_weight(r->cpu_calibration_map);
1092
1093     if ( smp_processor_id() == 0 )
1094     {
1095         while ( atomic_read(&r->nr_cpus) != (total_cpus - 1) )
1096             cpu_relax();
1097         r->master_stime = read_platform_stime();
1098         rdtscll(r->master_tsc_stamp);
1099         mb(); /* write r->master_* /then/ signal */
1100         atomic_inc(&r->nr_cpus);
1101         c->local_tsc_stamp = r->master_tsc_stamp;
1102     }
1103     else
1104     {
1105         atomic_inc(&r->nr_cpus);
1106         while ( atomic_read(&r->nr_cpus) != total_cpus )
1107             cpu_relax();
1108         mb(); /* receive signal /then/ read r->master_* */
1109         if ( boot_cpu_has(X86_FEATURE_CONSTANT_TSC) )
1110             wrmsrl(MSR_IA32_TSC, r->master_tsc_stamp);
1111         rdtscll(c->local_tsc_stamp);
1112     }
1113
1114     c->stime_local_stamp = get_s_time();
1115     c->stime_master_stamp = r->master_stime;
1116
1117     raise_softirq(TIME_CALIBRATE_SOFTIRQ);
1118 }


Best Regards,

Akio Takebe

  reply	other threads:[~2009-01-07 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07  9:41 hvm_set_callback_irq_level() deadlock? Akio Takebe
2009-01-07  9:59 ` Keir Fraser
2009-01-07 10:22   ` Akio Takebe [this message]
2009-01-07 10:31     ` Keir Fraser
2009-01-07 12:58       ` Akio Takebe

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=49648265.6070808@jp.fujitsu.com \
    --to=takebe_akio@jp.fujitsu.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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.