All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Martin Galvan <omgalvan.86@gmail.com>
Cc: Bharath Vedartham <linux.bhar@gmail.com>,
	kernelnewbies@kernelnewbies.org
Subject: Re: Setting CPU affinity for current process on kernel module?
Date: Fri, 13 Sep 2019 13:55:10 +0100	[thread overview]
Message-ID: <20190913125510.GA402888@kroah.com> (raw)
In-Reply-To: <CAN19L9Go1nem1LsEKyjwoA1jVJ2nAvewjZ6QvQr9BWbKE+=_hQ@mail.gmail.com>

On Fri, Sep 13, 2019 at 09:43:33AM -0300, Martin Galvan wrote:
> El vie., 13 sept. 2019 a las 1:50, Greg KH (<greg@kroah.com>) escribió:
> > I really hate to ask, but _why_ do you feel that this is the correct
> > solution to your problem?  What is the problem you are attempting to
> > solve by doing this?
> 
> I'm reading and comparing per-core MSR values.

And doing what with that information?  We have a msr driver for
userspace access to those values, does that not work correctly for you?

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2019-09-13 12:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11 18:52 Setting CPU affinity for current process on kernel module? Martin Galvan
2019-09-11 19:16 ` Bharath Vedartham
2019-09-11 19:19   ` Martin Galvan
2019-09-12  9:26     ` Bharath Vedartham
2019-09-12 14:03       ` Martin Galvan
2019-09-13  4:50         ` Greg KH
2019-09-13 12:43           ` Martin Galvan
2019-09-13 12:55             ` Greg KH [this message]
2019-09-13 12:56               ` Martin Galvan
2019-09-13 14:13                 ` Greg KH
2019-09-19  5:43                   ` R. Engür Pişirici

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=20190913125510.GA402888@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux.bhar@gmail.com \
    --cc=omgalvan.86@gmail.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.