From: Dave Jones <davej@redhat.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: changes to microcode update driver.
Date: Tue, 7 Oct 2003 14:54:17 +0100 [thread overview]
Message-ID: <20031007135417.GC11840@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.44.0310070352590.16056-100000@south.veritas.com>
On Tue, Oct 07, 2003 at 03:58:00AM -0700, Tigran Aivazian wrote:
> Hi guys,
>
> It's been a long time that I was going to send to Linux the patch with the
> following changes, but the birth of my first child intervened and caused
> delays (though can't call them "unexpected" :)
Congrats 8-)
> 1. Remove ->read() method for /dev/cpu/microcode device node and do not
> hold a copy of applied microcode chunks in kernel memory. In the days when
> we had a regular devfs file with a non-zero size this had at least some
> potential use but now this feature is almost useless and removing it would
> allow a lot of code cleanup and simplification.
>
> 2. remove MICROCODE_IOCFREE ioctl for freeing the copy of held microcode
> (because there won't be such copy, see 1.)
Assuming that it can be done without the old tools breaking, sounds good
to me. How will microcode_ctl -i react if you remove the ioctl ?
Folks _will_ upgrade kernels without updating userspace.
Dave
--
Dave Jones http://www.codemonkey.org.uk
next prev parent reply other threads:[~2003-10-07 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 10:58 RFC: changes to microcode update driver Tigran Aivazian
2003-10-07 11:02 ` Tigran Aivazian
2003-10-07 13:34 ` Giacomo A. Catenazzi
2003-10-07 13:48 ` Tigran Aivazian
2003-10-07 13:54 ` Dave Jones [this message]
2003-10-08 8:59 ` Tigran Aivazian
2003-10-08 10:07 ` Mikael Pettersson
2003-10-08 19:43 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 13:56 Nakajima, Jun
2003-10-07 15:56 ` Maciej Zenczykowski
2003-10-07 16:03 ` Tigran Aivazian
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=20031007135417.GC11840@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox