From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Purcareata Bogdan <b43198@freescale.com>
Cc: linux-rt-users@vger.kernel.org, scottwood@freescale.com,
Mihai Caraman <mihai.caraman@freescale.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: PPC: Convert openpic lock to raw_spinlock
Date: Tue, 17 Feb 2015 18:59:22 +0100 [thread overview]
Message-ID: <20150217175922.GC26177@linutronix.de> (raw)
In-Reply-To: <20150217175317.GB26177@linutronix.de>
* Sebastian Andrzej Siewior | 2015-02-17 18:53:17 [+0100]:
>* Purcareata Bogdan | 2015-02-17 14:27:44 [+0200]:
>
>>Ping?
>>
>>On 02.02.2015 11:35, Purcareata Bogdan wrote:
>>>Ping?
>
>No body?
bah! That mutt thing is too fast.
The raw conversation looks sane and could go upstream. This other chunk:
|+#if defined(CONFIG_PREEMPT_RT_FULL) && defined(CONFIG_KVM_MPIC)
|+/* Limit the number of vcpus due to in-kernel mpic concurrency */
|+#define KVM_MAX_VCPUS 4
|+#define KVM_MAX_VCORES 4
|+#else
| #define KVM_MAX_VCPUS NR_CPUS
| #define KVM_MAX_VCORES NR_CPUS
|+#endif
should be a separate patch. Please repost including ppc ml.
This remains of my multiple-MSI patch which someone other posted a while
ago. What happend to it?
Sebatian
next prev parent reply other threads:[~2015-02-17 17:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 9:39 [PATCH] KVM: PPC: Convert openpic lock to raw_spinlock Bogdan Purcareata
2015-02-02 9:35 ` Purcareata Bogdan
2015-02-17 12:27 ` Purcareata Bogdan
2015-02-17 17:53 ` Sebastian Andrzej Siewior
2015-02-17 17:59 ` Sebastian Andrzej Siewior [this message]
2015-02-18 8:31 ` Purcareata Bogdan
2015-02-18 8:40 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2014-09-11 19:25 Bogdan Purcareata
2014-09-11 13:06 ` Bogdan Purcareata
2014-09-11 18:19 ` Scott Wood
2014-09-11 18:19 ` Scott Wood
2014-09-12 14:12 ` bogdan.purcareata
2014-09-12 14:12 ` bogdan.purcareata
2014-09-12 17:50 ` Scott Wood
2014-09-12 17:50 ` Scott Wood
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=20150217175922.GC26177@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=b43198@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mihai.caraman@freescale.com \
--cc=scottwood@freescale.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.