All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pankaj Gupta <pagupta@redhat.com>
To: linux-rt-users@vger.kernel.org
Subject: Query - state of memory hotplug with RT kernel
Date: Thu, 2 Jun 2016 06:10:41 -0400 (EDT)	[thread overview]
Message-ID: <420969271.56780563.1464862241604.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1997236940.56779393.1464861408686.JavaMail.zimbra@redhat.com>

Hello,

Recently, I have been debugging some of the issues with memory 
hotplug with RT kernel. I want to know state of memory hotplug 
with RT kernel and if there are any known issues or work going
on upstream?

I came to know that there is rework of 'cpu hotplug' going on.
Not sure about 'memory hotplug'.

Any inputs or pointers on this?

Best regards,
Pankaj

       reply	other threads:[~2016-06-02 10:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1997236940.56779393.1464861408686.JavaMail.zimbra@redhat.com>
2016-06-02 10:10 ` Pankaj Gupta [this message]
2016-06-03 16:04   ` Query - state of memory hotplug with RT kernel Sebastian Andrzej Siewior
2016-06-08  7:05     ` Pankaj Gupta
2016-06-09 13:05       ` Sebastian Andrzej Siewior
2016-06-17 13:08         ` Pankaj Gupta

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=420969271.56780563.1464862241604.JavaMail.zimbra@redhat.com \
    --to=pagupta@redhat.com \
    --cc=linux-rt-users@vger.kernel.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.