AIX 6.1, POWER5 and Spectre/Meltdown Post: 303010868

7 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

hard disk meltdown

I had an issue with a second hard disk in my machine. I have a sparc station running solaris 7. It was working fine but now it wont mount on boot up and when you try to mount it manually it gives an I/O error. I tried a different disk as a control which was fine. What I want to know is if my...

2. AIX

Problem with knlist in AIX 5.3 for Power5 processor

Hi all, I have a AIX 5.3 Installation on the Power5 processor. I am using the knlist API for getting the details of the CPU details like user cpu, kernel cpu, idle cpu and wait cpu. My code is working fine on other Installations of AIX like PowerPC_POWER4 but it is giving wrong values on Power5...

3. AIX

Upgrading Power5 from 5.3 to...

I have a power5 that I would like to update and bring everything forward. I am wondering about trouble-free upgrades. Is it better to go 5.3 -> 7 or 5.3 ->6 ->7? The power5 box is behind and hopefully can learn from experiences here. Thanks.

4. AIX

POWER5+ 2.1Gz cpu wattage ?

Hello, What is wattage of POWER5+ 2.1Gz CPU ? It's dual-core 90nm chip. At least approximately ? thanks, Vilius

5. AIX

Power5 9111-520 reload of AIX 6.1 - help needed

Hello all, I am hoping someone can point me in the right direction here. We had a machine running AIX 6.1 that someone completely corrupted, so we decided to re-load it from media. I was able to boot into DVD media, select options for complete (destructive) install, AIX standard, etc. The...

6. War Stories

Linus Torvalds reply about Meltdown and Spectre.

Apologies if this is the wrong forum but... ...This is hard hitting stuff. LKML: Linus Torvalds: Re: x86/enter: Create macros to restrict/unrestrict Indirect Branch Speculation

7. What is on Your Mind?

Meltdown and Spectre CPU bugs

This seems a bit serious: Meltdown, Spectre: The password theft bugs at the heart of Intel CPUs � The Register Vulnerability Note VU#584653 - CPU hardware vulnerable to side-channel attacks Project Zero: Reading privileged memory with a side-channel

LEARN ABOUT DEBIAN

stg-uncommit

STG-UNCOMMIT(1) 						   StGit Manual 						   STG-UNCOMMIT(1)

NAME

       stg-uncommit - Turn regular git commits into StGit patches

SYNOPSIS

       stg uncommit <patch-name-1> [<patch-name-2> ...]
       stg uncommit -n NUM [<prefix>]
       stg uncommit -t <committish> [-x]

DESCRIPTION

       Take one or more git commits at the base of the current stack and turn them into StGIT patches. The new patches are created as applied
       patches at the bottom of the stack. This is the opposite of stg commit.

       By default, the number of patches to uncommit is determined by the number of patch names provided on the command line. First name is used
       for the first patch to uncommit, i.e. for the newest patch.

       The -n/--number option specifies the number of patches to uncommit. In this case, at most one patch name may be specified. It is used as
       prefix to which the patch number is appended. If no patch names are provided on the command line, StGIT automatically generates them based
       on the first line of the patch description.

       The -t/--to option specifies that all commits up to and including the given commit should be uncommitted.

       Only commits with exactly one parent can be uncommitted; in other words, you can't uncommit a merge.

OPTIONS

       -n NUMBER, --number NUMBER
	   Uncommit the specified number of commits.

       -t TO, --to TO
	   Uncommit to the specified commit.

       -x, --exclusive
	   Exclude the commit specified by the --to option.

STGIT

       Part of the StGit suite - see linkman:stg[1]

StGit								    03/13/2012							   STG-UNCOMMIT(1)