search for: pie

On Wed, Oct 11, 2017 at 2:34 PM, Tom Lendacky <thomas.lendacky at amd.com> wrote: > On 10/11/2017 3:30 PM, Thomas Garnier wrote: >> Changes: >> - patch v1: >> - Simplify ftrace implementation. >> - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. >> - rfc v3: >> - Use --emit-relocs instead of -pie to reduce dynamic relocation space on >> mapped memory. It also simplifies the relocation process. >> - Move the start the module section next to the kernel. Remove the need for >>...

On Wed, Oct 11, 2017 at 2:34 PM, Tom Lendacky <thomas.lendacky at amd.com> wrote: > On 10/11/2017 3:30 PM, Thomas Garnier wrote: >> Changes: >> - patch v1: >> - Simplify ftrace implementation. >> - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. >> - rfc v3: >> - Use --emit-relocs instead of -pie to reduce dynamic relocation space on >> mapped memory. It also simplifies the relocation process. >> - Move the start the module section next to the kernel. Remove the need for >>...

Hey, i'd like to compose a clock-like looking plot composed out of two circles, each showing the length of a period (to compare them). first, to do so, it looked the easiest by using pie(), just puting multiple pie-charts over each other. the problem is that once the second pie is drawn, it replaces the first one. does anybody know how to add a second, smaller pie over an existing one, like a layer? thanks, lars

On 10/11/2017 3:30 PM, Thomas Garnier wrote: > Changes: > - patch v1: > - Simplify ftrace implementation. > - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. > - rfc v3: > - Use --emit-relocs instead of -pie to reduce dynamic relocation space on > mapped memory. It also simplifies the relocation process. > - Move the start the module section next to the kernel. Remove the need for > -mcmodel=large on m...

...Oct 11, 2017 at 2:34 PM, Tom Lendacky <thomas.lendacky at amd.com> wrote: >> On 10/11/2017 3:30 PM, Thomas Garnier wrote: >>> Changes: >>> - patch v1: >>> - Simplify ftrace implementation. >>> - Use gcc mstack-protector-guard-reg=%gs with PIE when possible. >>> - rfc v3: >>> - Use --emit-relocs instead of -pie to reduce dynamic relocation space on >>> mapped memory. It also simplifies the relocation process. >>> - Move the start the module section next to the kernel. Remove the nee...

On Thu, Feb 27, 2020 at 04:00:45PM -0800, Thomas Garnier wrote: > Minor changes based on feedback and rebase from v10. > > Splitting the previous serie in two. This part contains assembly code > changes required for PIE but without any direct dependencies with the > rest of the patchset. > > Note: Using objtool to detect non-compliant PIE relocations is not yet > possible as this patchset only includes the simplest PIE changes. > Additional changes are needed in kvm, xen and percpu code. > >...

On Thu, Feb 27, 2020 at 04:00:45PM -0800, Thomas Garnier wrote: > Minor changes based on feedback and rebase from v10. > > Splitting the previous serie in two. This part contains assembly code > changes required for PIE but without any direct dependencies with the > rest of the patchset. > > Note: Using objtool to detect non-compliant PIE relocations is not yet > possible as this patchset only includes the simplest PIE changes. > Additional changes are needed in kvm, xen and percpu code. > >...

...implementation. - Edit commit description to explain better where the kernel can be located. - Streamlined the testing done on each patch proposal. Always testing hibernation, suspend, ftrace and kprobe to ensure no regressions. - patch v3: - Update on message to describe longer term PIE goal. - Minor change on ftrace if condition. - Changed code using xchgq. - patch v2: - Adapt patch to work post KPTI and compiler changes - Redo all performance testing with latest configs and compilers - Simplify mov macro on PIE (MOVABS now) - Reduce GOT footprint - patch v1:...

Dear all, I'd like to produce a simple pie chart for a customer (I know it's bad but they insist), and I have some difficulties setting the initial angle. For example: pie(c(60, 40), init.angle=14) and pie(c(80, 20), init.angle=338) both present the slices in the same direction, where: pie(c(60, 40)) pie(c(80, 20)) present the s...

Changes: - patch v5: - Adapt new crypto modules for PIE. - Improve per-cpu commit message. - Fix xen 32-bit build error with .quad. - Remove extra code for ftrace. - patch v4: - Simplify early boot by removing global variables. - Modify the mcount location script for __mcount_loc intead of the address read in the ftrace implementati...

Greetings all! I'm facing a puzzle I have not been able to solve. I need to make an EPS of a pie-chart (Yes, I know; please don't bother to tell me! I just need to ...). I'm trying to do it with pie(), and I want to have just the plain pie-chart with no annotations. So far so good: "labels=rep(NA,...)" will do it. But I want to have it output to an EPS file with the Boundin...

Hello R usuer, The code given below superimposes a pie diagram on another plot containing some points. However, I would like to center the pie diagram on the xy location on the plot, but not on the center. is there any way to re-center pic diagram. Any suggestion or better alternative are highly appreciated. Thank you in advance for your help. Regards...

Dear all, After going through the Lattice doc and R-help list and google, I got the feeling that there is no function in lattice or other package to compute a pie chart object of class "trellis". Although pie charts are obviously not considered optimal even in the pie() doc ;-) , pie chart trellis objects would be easy positioned e.g. over a map drawn with the grids package. Can anybody confirm this absence or indicate a package/function able...

Hi all, I am looking to create a pie chart from a given column in a .csv file. My class variables are as follows: entry_type, uniquekey, types, title, url, abstract, journal, author, month, year, howpublished So say I want to export a pie chart that groups together all entries under 'types' e.g. 3 x statistics 2x educati...

..., DD.com..load = c(0L, 0L), Neighbor.search = c("3.7", "3. 1"), Launch.PP.GPU.ops. = c("0. 1", "0"), Comm..coord. = c("1 .6", "1 .0"), Force = c("1 . 5", "1 .2" ), Wait...Comm..F = c("1 .3", "1 .7"), PIE.mesh = c(65.6, 70.9 ), Wait.Bonded.GPU = c(0L, 0L), wait.GPU.NB.nonloc. = c(0L, 0L ), Wait.GPU.NB.local = c(0L, 0L), NB.X.F.buffer.ops. = c(7.3, 4.4), Write.traje = c(0.3, 0.3), Update = c(6.3, 4.3), Constraints = c(8.9, 9.7), Comm..energies = c(0.9, 0.9), PIE.redist..X.F = c("8. 1", &quo...

Hi, despite the fact that pie charts often fail, I'll draw them anyway (in a case were they are not fail ;-) ). Does anybody know a package/methods which can draw pie of pie or bar of pie charts similar to that in MS Excel? -- Kind regards, Mathias

Hi all, Is there a way to draw 3D pie with R (like excel does)? I know how to do it in 2D, just by using pie(something)... I know it isn't the best way to represent data, but people are sometimes more interested by the look and feel than by the accuracy of the results... If there is no way, have you another suggestion ?...

...sFactors=FALSE, header=TRUE)) > d11 X Domain.decomp. DD.com..load Neighbor.search Launch.PP.GPU.ops. Comm..coord. 1 SYCL 2. 1 0 3.7 0. 1 1 .6 2 CUDA 2 0 3. 1 0 1 .0 Force Wait...Comm..F PIE.mesh Wait.Bonded.GPU wait.GPU.NB.nonloc. 1 1 . 5 1 .3 65.6 0 0 2 1 .2 1 .7 70.9 0 0 Wait.GPU.NB.local NB.X.F.buffer.ops. Write.traje Update Constraints Comm..energies 1 0 7....

Hi again! I put this question in another topics post before but I fear it might drown there. Is it possible to have transparent / alpha blended colors for pie charts? I am using the pies in a map of pies and those pies are sometimes overlapping so it would be great to see if another pie lies beneath. Thanks, Werner

Minor changes based on feedback and rebase from v8. Splitting the previous serie in two. This part contains assembly code changes required for PIE but without any direct dependencies with the rest of the patchset. Changes: - patch v9 (assembly): - Moved to relative reference for sync_core based on feedback. - x86/crypto had multiple algorithms deleted, removed PIE changes to them. - fix typo on comment end line. - patch v8 (assemb...