Avi Kivity wrote:
Arjan van de Ven wrote:
Can't it be done by a helper function using a timer and a signal (or
whatever mechanism we use to wake up vcpus)?
one could do that but it's not optimal; if the process DOES get waken up
earlier, it should take the interrupt then immediat
Arjan van de Ven wrote:
Can't it be done by a helper function using a timer and a signal (or
whatever mechanism we use to wake up vcpus)?
one could do that but it's not optimal; if the process DOES get waken up
earlier, it should take the interrupt then immediately, so that it
doesn't have
> Can't it be done by a helper function using a timer and a signal (or
> whatever mechanism we use to wake up vcpus)?
one could do that but it's not optimal; if the process DOES get waken up
earlier, it should take the interrupt then immediately, so that it
doesn't have to wake up again when the
Arjan van de Ven wrote:
Somthing else that came up in a conversation with Dor: the need for a
clean way to raise a guest interrupt. The guest may be sleeping in
userspace, scheduled out, or running on another cpu (and requiring an
ipi to get it out of guest mode).
yeah it'd be nice if I
> Somthing else that came up in a conversation with Dor: the need for a
> clean way to raise a guest interrupt. The guest may be sleeping in
> userspace, scheduled out, or running on another cpu (and requiring an
> ipi to get it out of guest mode).
yeah it'd be nice if I could just call a fun
Arjan van de Ven wrote:
- execution of hypercall handlers outside vcpu_load() (so they are
> preemptible and sleepable)
I don't need this; most of my hypercalls are non-blocking. The ones that
are can already undo the load themselves, no big deal.
I don't really like exposing the vcpu_
On Thu, 2007-02-22 at 12:40 +0200, Avi Kivity wrote:
> Arjan van de Ven wrote:
> >> I have Ingo's network PV hypercalls to commit in my piplien.
> >>
> >
> > I have 5 or so pending as well :)
> > can't wait for the infrastructure to be there so that it's relatively
> > easy to add my paravirt
Arjan van de Ven wrote:
I have Ingo's network PV hypercalls to commit in my piplien.
I have 5 or so pending as well :)
can't wait for the infrastructure to be there so that it's relatively
easy to add my paravirt block driver
I can't wait for your pv block driver :)
What do you think
Joerg Roedel wrote:
On Thu, Feb 22, 2007 at 02:17:54AM -0800, Dor Laor wrote:
I have Ingo's network PV hypercalls to commit in my piplien.
Till then we can just add the test hypercall:
case __NR_hypercall_test:
printk(KERN_DEBUG "%s __NR_hypercall_test\n",
__FUNCTION__
> >
>
> I have Ingo's network PV hypercalls to commit in my piplien.
I have 5 or so pending as well :)
can't wait for the infrastructure to be there so that it's relatively
easy to add my paravirt block driver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
On Thu, Feb 22, 2007 at 02:17:54AM -0800, Dor Laor wrote:
> I have Ingo's network PV hypercalls to commit in my piplien.
> Till then we can just add the test hypercall:
> case __NR_hypercall_test:
> printk(KERN_DEBUG "%s __NR_hypercall_test\n",
> __FUNCTION__);
> r
>
>Pavel Machek wrote:
>> On Mon 2007-02-19 10:30:52, Avi Kivity wrote:
>>
>>> Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
>>>
>>
>> changelog?
>>
>>
>
>Well, I can't think of anything to add beyond $subject. The patch adds
>calls from the arch-dependent hypercall handlers to a new arch
>indepen
12 matches
Mail list logo
