From: Corey Minyard <cminyard@mvista.com>
To: Mau Z <zmau1962@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Can PAX and Rt-patch co-exist ?
Date: Fri, 02 May 2014 12:28:42 -0500 [thread overview]
Message-ID: <5363D5CA.2020102@mvista.com> (raw)
In-Reply-To: <CAPFcPTJLcZ3RJ0VsUvEJbtx1tj4_y6P31YhRiTW+OnsfUHT_9Q@mail.gmail.com>
On 05/02/2014 02:40 AM, Mau Z wrote:
> Thanks
>
> The answer is very surprising.
> I would assume that more than one person would have such an experience.
Well, the LTSI organization may have done it. That's all I can think
of, though.
>
>
> I am curious regarding the magnitude of work to be done. I am
> especially intersted what happens when you have to handle another
> Linux version for your distribution.
>
> Is this job done just once (for one specific Linux version) ?
Once for a specific Linux version, 3.10.
> or
> You do the job once, and then do the same fixes on the other Linux
> version (more or less) ?
> or
> You have to do the same job all over again in every linux version ?
We will on the next version we release, yes.
>
>
> Is the following discription correct ?
> Basically the job is
> 1) Download kernel
> 2) apply RT-patch
> 3) apply PAX patch
> 4) compile and fix warnings and errors
Well, there's testing :). But basically yes. Resolving the conflicts
is the biggest deal, really, in the above process. And testing is a lot
bigger than that :).
We integrate a lot of other things, so it's hard to remember the
specific RT/PaX issues.
-corey
>
> Thanks
> again
> zmau
>
>
> On Thu, May 1, 2014 at 2:53 AM, Corey Minyard <cminyard@mvista.com> wrote:
>> On 04/30/2014 05:47 PM, Mau Z wrote:
>>> I have some more questions concerning the relation between PAX and the
>>> RT-Patch :
>>> A) Can they work together ?
>> It can be made to work. We have it working together in our distribution.
>>
>>> B) Do you know if it matters which patch is applied first ?
>> Not really.
>>
>>> C) Is there any documentation about this subject ?
>> None that I know of. I imagine that I'm the only person who has ever
>> done this.
>>
>> There are some conflicts (a few are non-trivial, but not excessively
>> complicated, IIRC). But it's not something insurmountable. You do have
>> to have a fairly good understanding of kernel code.
>>
>> -corey
>>
>>>
>>> Thanks
>>> zmau
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-02 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 22:47 Can PAX and Rt-patch co-exist ? Mau Z
2014-04-30 23:53 ` Corey Minyard
2014-05-02 7:40 ` Mau Z
2014-05-02 17:28 ` Corey Minyard [this message]
2014-05-03 11:49 ` Mau Z
2014-05-05 13:20 ` Corey Minyard
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=5363D5CA.2020102@mvista.com \
--to=cminyard@mvista.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=zmau1962@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.