---------- Forwarded message ----------
From: <kernelnewbies-request at kernelnewbies.org>
Date: Mon, Feb 15, 2016 at 5:40 AM
Subject: Kernelnewbies Digest, Vol 63, Issue 20
To: kernelnewbies at kernelnewbies.org
Send Kernelnewbies mailing list submissions to
kernelnewbies at kernelnewbies.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
or, via email, send a message with subject or body 'help' to
kernelnewbies-request at kernelnewbies.org
You can reach the person managing the list at
kernelnewbies-owner at kernelnewbies.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Kernelnewbies digest..."
Today's Topics:
1. Re: current during interrupt servicing (Mulyadi Santosa)
2. Merge conflict (YU Bo)
3. Re: Merge conflict (Roger H Newell)
4. Re:Re: Merge conflict (YU Bo)
----------------------------------------------------------------------
Message: 1
Date: Mon, 15 Feb 2016 01:10:53 +0700
From: Mulyadi Santosa <mulyadi.santosa at gmail.com>
Subject: Re: current during interrupt servicing
To: "tobaccopipeyoyo ." <tobaccopipeyoyo at gmail.com>
Cc: kernelnewbies <kernelnewbies at kernelnewbies.org>
Message-ID:
<CAGdaadYgnA7JwfgUCxa=hiJjQm4Oz+rDy-htZCi6cdw7O8WFgg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Sun, Feb 14, 2016 at 9:16 AM, tobaccopipeyoyo . <
tobaccopipeyoyo at gmail.com> wrote:
> Hi,
> I'm new to kernel programming, currently started ldd book
> For the current process it says that global item current returns the
> task_struct of the currently running process.
>
> What if I refer this global during interrupt servicing?
> What will happen? What should I expect.
>
> Thanks,
> tpyy
>
>
Hi...
during interrupt servicing, "current" will give you last process' data
structure that's get interrupted by the interrupt. Of course, this is per
cpu context, so if you are in SMP situation, current will return task
struct in that CPU only.
The essential thing in interrupt servicing is: interrupt handler runs on
behalf of current running process.
Hopefully I still recall all these correctly.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
Hi Mulyadi,
I disagree with the statement you made here that
"interrupt handler runs on behalf of current running process".
Your statement is valid for system calls (software interrupt) but not for
the real "interrupt"
Interrupt handler are nowhere related to any process. They run their own
without caring about
which process was running.
--- Vishwas
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160215/005f337f/attachment-0001.html
------------------------------
Message: 2
Date: Mon, 15 Feb 2016 07:46:36 +0800 (CST)
From: "YU Bo" <yuzibode at 126.com>
Subject: Merge conflict
To: "kernelnewbies at kernelnewbies.org"
<kernelnewbies at kernelnewbies.org>
Message-ID: <50a639e9.361.152e22dc5ea.Coremail.yuzibode at 126.com>
Content-Type: text/plain; charset="gbk"
Hi,
Some days ago i followed the tips:
http://kernelnewbies.org/FirstKernelPatch
git clone greg's git tree and built branch first-patch.
Due to my first patch that fixes coding style reported
by checkptch.pl didn't applied,so i intend to rebase my
git branch first-patch.The question i encounter is:
==================git command && output========
yubo at debian:~/maintree/staging$ git rebase first-patch
It looks like git-am is in progress. Cannot rebase.
yubo at debian:~/maintree/staging$ git am --abort
You seem to have moved HEAD since the last 'am' failure.
Not rewinding to ORIG_HEAD
yubo at debian:~/maintree/staging$ git rebase first-patch
First, rewinding head to replay your work on top of it...
Applying: ovl: default permissions
Using index info to reconstruct a base tree...
Falling back to patching base and 3-way merge...
----
Auto-merging drivers/gpu/drm/i915/intel_display.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_display.c
Failed to merge in the changes.
Patch failed at 0010 drm/i915: Only run commit when crtc is active, v2.
Is there something with wrong?
Thanks in advance for the noisy.
--
Best Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160215/a9f6b611/attachment-0001.html
------------------------------
Message: 3
Date: Sun, 14 Feb 2016 20:21:40 -0330
From: Roger H Newell <newell.roger at gmail.com>
Subject: Re: Merge conflict
To: YU Bo <yuzibode at 126.com>
Cc: kernelnewbies at kernelnewbies.org
Message-ID:
<CAEE9rjYv7AxAeMZkVCphwW61QNi3VDyETMw+F87PdTRkAP6N6w at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I think you want to have first-patch checked out and rebase
origin/staging-testing ? You mite also consider checking out
staging-testing first and run git fetch origin.
On Feb 14, 2016 8:17 PM, "YU Bo" <yuzibode at 126.com> wrote:
>
> Hi,
> Some days ago i followed the tips:
> http://kernelnewbies.org/FirstKernelPatch
> git clone greg's git tree and built branch first-patch.
> Due to my first patch that fixes coding style reported
> by checkptch.pl didn't applied,so i intend to rebase my
> git branch first-patch.The question i encounter is:
> ==================git command && output========
> yubo at debian:~/maintree/staging$ git rebase first-patch
> It looks like git-am is in progress. Cannot rebase.
> yubo at debian:~/maintree/staging$ git am --abort
> You seem to have moved HEAD since the last 'am' failure.
> Not rewinding to ORIG_HEAD
> yubo at debian:~/maintree/staging$ git rebase first-patch
> First, rewinding head to replay your work on top of it...
> Applying: ovl: default permissions
> Using index info to reconstruct a base tree...
> Falling back to patching base and 3-way merge...
> ----
> Auto-merging drivers/gpu/drm/i915/intel_display.c
> CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_display.c
> Failed to merge in the changes.
> Patch failed at 0010 drm/i915: Only run commit when crtc is active, v2.
>
> Is there something with wrong?
> Thanks in advance for the noisy.
> --
> Best Regards
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160214/dd794278/attachment-0001.html
------------------------------
Message: 4
Date: Mon, 15 Feb 2016 08:10:35 +0800 (CST)
From: "YU Bo" <yuzibode at 126.com>
Subject: Re:Re: Merge conflict
To: "Roger H Newell" <newell.roger at gmail.com>
Cc: kernelnewbies at kernelnewbies.org
Message-ID: <35d0bb5e.45d.152e243ba6a.Coremail.yuzibode at 126.com>
Content-Type: text/plain; charset="gbk"
Hi,
I just have checkouted origin/staging-testing and git rebase
first-patch.Now,
=============git command && output==============
yubo at debian:~/maintree/staging$ git branch -a
* (no branch)
first-patch
staging-next
staging-testing
remotes/origin/HEAD -> origin/master
remotes/origin/master
remotes/origin/staging-linus
remotes/origin/staging-next
remotes/origin/staging-testing
remotes/origin/test
ubo at debian:~/maintree/staging$ git fetch origin
remote: Counting objects: 273, done.
remote: Compressing objects: 100% (273/273), done.
remote: Total 273 (delta 160), reused 0 (delta 0)
Receiving objects: 100% (273/273), 298.64 KiB | 196 KiB/s, done.
Resolving deltas: 100% (160/160), done.
>From git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
2cdb82c..d9750a2 staging-next -> origin/staging-next
yubo at debian:~/maintree/staging$ git checkout staging-testing
drivers/gpu/drm/i915/intel_display.c: needs merge
error: you need to resolve your current index first
===============end==================
--
Best Regards
? 2016-02-15 07:51:40?"Roger H Newell" <newell.roger at gmail.com> ???
I think you want to have first-patch checked out and rebase
origin/staging-testing ? You mite also consider checking out
staging-testing first and run git fetch origin.
On Feb 14, 2016 8:17 PM, "YU Bo" <yuzibode at 126.com> wrote:
>
> Hi,
> Some days ago i followed the tips:
> http://kernelnewbies.org/FirstKernelPatch
> git clone greg's git tree and built branch first-patch.
> Due to my first patch that fixes coding style reported
> by checkptch.pl didn't applied,so i intend to rebase my
> git branch first-patch.The question i encounter is:
> ==================git command && output========
> yubo at debian:~/maintree/staging$ git rebase first-patch
> It looks like git-am is in progress. Cannot rebase.
> yubo at debian:~/maintree/staging$ git am --abort
> You seem to have moved HEAD since the last 'am' failure.
> Not rewinding to ORIG_HEAD
> yubo at debian:~/maintree/staging$ git rebase first-patch
> First, rewinding head to replay your work on top of it...
> Applying: ovl: default permissions
> Using index info to reconstruct a base tree...
> Falling back to patching base and 3-way merge...
> ----
> Auto-merging drivers/gpu/drm/i915/intel_display.c
> CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_display.c
> Failed to merge in the changes.
> Patch failed at 0010 drm/i915: Only run commit when crtc is active, v2.
>
> Is there something with wrong?
> Thanks in advance for the noisy.
> --
> Best Regards
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160215/5c0d9abc/attachment.html
------------------------------
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies at kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
End of Kernelnewbies Digest, Vol 63, Issue 20
*********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160215/8465d9cd/attachment-0001.html